Arch Linux

Ramses de Norre

Member

From: Leuven - Belgium

Registered: 2007-03-27

Posts: 1,289

Ext4 bad header/extent

I'm suddenly seeing these messages in dmesg:

EXT4-fs error (device sda2): ext4_ext_check_inode:406: inode #3760218: comm parcellite: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
EXT4-fs error (device sda2): ext4_ext_check_inode:406: inode #3760208: comm parcellite: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
EXT4-fs error (device sda2): ext4_ext_check_inode:406: inode #3760218: comm notification-da: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
EXT4-fs error (device sda2): ext4_ext_check_inode:406: inode #3760208: comm notification-da: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
EXT4-fs error (device sda2): ext4_ext_check_inode:406: inode #3760218: comm xfce4-power-man: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
EXT4-fs error (device sda2): ext4_ext_check_inode:406: inode #3760208: comm xfce4-power-man: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
EXT4-fs error (device sda2): ext4_ext_check_inode:406: inode #3760218: comm dropbox: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
EXT4-fs error (device sda2): ext4_ext_check_inode:406: inode #3760208: comm dropbox: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
EXT4-fs error (device sda2): ext4_ext_check_inode:406: inode #3760218: comm firefox: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
EXT4-fs error (device sda2): ext4_ext_check_inode:406: inode #3760208: comm firefox: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

Details for one of those inodes:

% debugfs -R 'stat <3760208>' /dev/disk/by-label/home
debugfs 1.41.14 (22-Dec-2010)
Inode: 3760208   Type: regular    Mode:  0644   Flags: 0x80000
Generation: 231468018    Version: 0x00000001
User:  1000   Group:   100   Size: 42
File ACL: 0    Directory ACL: 0
Links: 1   Blockcount: 0
Fragment:  Address: 0    Number: 0    Size: 0
ctime: 0x4b2a09ff -- Thu Dec 17 11:37:51 2009
atime: 0x4d909367 -- Mon Mar 28 15:55:51 2011
mtime: 0x490976f8 -- Thu Oct 30 09:57:28 2008
EXTENTS:

and these worry me a lot! I've ran fsck on the partition (multiple times) which says that the filesystem has been modified, but the errors return every time. Does anyone have any idea what this could be?
I've been running 2.6.38 and 2.6.38.1 from testing but to be sure I downgraded to 2.6.37.5, which didn't change anything. e2fsprogs is at the current version from core, 1.41.14-1.

I do have backups from my data, but this really disturbs me!

Also, the only hits on google where from problems that should've been solved many kernel releases ago.