[wplug] Ext3 filesystem errors with RAID 1 USB drives

Jonathan Billings billings at negate.org
Sun Feb 27 21:07:33 EST 2011


On Feb 27, 2011, at 9:57 AM, Max Putas wrote:
> [1601863.389701] init_special_inode: bogus i_mode (174771) for inode
> dm-0:45777888  (Hundreds of this message)
> [1596380.877215] EXT3-fs error (device dm-0): htree_dirblock_to_tree:
> bad entry in directory #13074636: rec_len % 4 != 0 - offset=0,
> inode=2242678265, rec_len=34181, name_len=133  (This one quite often)
> [   22.040754] dm-0: rw=0, want=22098027816, limit=1953513472 (Couple
> dozen of these errors)
> [   21.718752] init_special_inode: bogus i_mode (31463) for inode
> dm-0:45385118 (Couple of these)

These errors indicate that you've got bad data in your filesystem metadata: 'init_special_inode: bogus i_mode' means the kernel has encountered inodes that it has no idea what to do with.  You most likely need to run a fsck on the filesystem.

I'd check the RAID to make sure it's operational, and possibly check the disks themselves for problems.  As for the source of the corruption, as other people have said, it's probably a noisy USB bus.  You might want to check the amount of bad blocks on the disks, run the SMART tests on your disks with smartctl.

--
Jonathan Billings <billings at negate.org>




More information about the wplug mailing list