Comment 34 for bug 992424

Revision history for this message
Charles Forsyth (charles-forsyth) wrote :

Today's contribution, after hardly any work (allowing for overnight locatedb updates and anything else the cron might do.

[70391.556798] EXT4-fs error (device sda1): __ext4_ext_check_block:472: inode #560844: comm Chrome_CacheThr: bad header/extent: invalid magic - magic 3262, entries 13113, max 14435(0), depth 12385(0)
[70391.556806] Aborting journal on device sda1-8.
[70391.556876] EXT4-fs (sda1): Remounting filesystem read-only
[70391.556881] EXT4-fs error (device sda1) in ext4_ext_remove_space:2790: IO failure
[70391.556956] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4550: Journal has aborted
[70391.557068] EXT4-fs error (device sda1) in ext4_ext_truncate:4308: Journal has aborted
[70391.557159] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4550: Journal has aborted
[70391.557260] EXT4-fs error (device sda1) in ext4_orphan_del:2491: Journal has aborted
[70391.557360] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4550: Journal has aborted

Similar trace back.

I find it interesting that the locatedb is often supposedly corrupt at the same time:

% locate cron
locate: `/var/lib/mlocate/mlocate.db' does not seem to be a mlocate database

After a reboot and a file system check, however, it's fine.

Some output from debugfs:
dumpe2fs 1.42 (29-Nov-2011)
Filesystem volume name: <none>
Last mounted on: /
Filesystem UUID: 4bfde6cd-c859-40f6-8848-9ecaa5d93265
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr dir_index filetype needs_recovery extent sparse_super large_file uninit_bg
Filesystem flags: signed_directory_hash
Default mount options: discard
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 2215168
Block count: 4442364
Reserved block count: 222117
Free blocks: 381539
Free inodes: 1611147
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16288
Inode blocks per group: 509
Last mount time: Wed Oct 17 14:44:21 2012
Last write time: Thu Oct 18 10:20:17 2012
Mount count: 1
Maximum mount count: 30
Last checked: Wed Oct 17 15:40:55 2012
Check interval: 0 (<none>)
Lifetime writes: 437 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
First orphan inode: 560844
Default directory hash: half_md4
Directory Hash Seed: 51028ff9-6909-473c-bbb9-01690bdd9a66
Journal backup: inode blocks
FS Error count: 7
First error time: Thu Oct 18 10:20:17 2012
First error function: __ext4_ext_check_block
First error line #: 472
First error inode #: 560844
First error block #: 0
Last error time: Thu Oct 18 10:20:17 2012
Last error function: ext4_reserve_inode_write
Last error line #: 4550
Last error inode #: 560844
Last error block #: 0
Journal features: journal_incompat_revoke
Journal size: 128M
Journal length: 32768
Journal sequence: 0x00004065
Journal start: 24962

debugfs: stat <560844>
Inode: 560844 Type: regular Mode: 0600 Flags: 0x80000
Generation: 2592733553 Version: 0x00000001
User: 1000 Group: 1000 Size: 0
File ACL: 0 Directory ACL: 0
Links: 0 Blockcount: 88
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x507fc9d1 -- Thu Oct 18 10:20:17 2012
atime: 0x507eca54 -- Wed Oct 17 16:10:12 2012
mtime: 0x507eca54 -- Wed Oct 17 16:10:12 2012
dtime: 0x001069cf -- Tue Jan 13 11:47:43 1970
EXTENTS:
(ETB0):1121648

debugfs: blocks <560844>
1121648

debugfs: bmap <560844> 0
argv[0]: Corrupt extent header while mapping logical block 0