Filesystem Corruption revisited

I believe there is a kernel issue (at least with my kernel). Less then
24 hours after fixing the /dev/hda8 filesystem which was fubar, I now
have BOTH hda8 and hda9 go read-only (the first symptom I see).

Here is some information from the logs. I am seeing a ton of the
following error:

Dec 28 06:03:57 anime kernel: evbug.c: Event. Dev: adb2:2.02/input,
Type: 1, Code: 57, Value: 1
Dec 28 06:03:57 anime kernel: evbug.c: Event. Dev: adb2:2.02/input,
Type: 0, Code: 0, Value: 0

This looks like something with the adb driver (keyboard/mouse are
using it). Not sure why it would affect filesystems.

I also get this one. I am running a static kernel, so I am not sure
why this is even happening. Again, I do not see how it would affect
filesystems:

Dec 27 21:27:21 anime modprobe: FATAL: Could not load  
lib/modules/2.6.9-gentoo-r1/modules.dep: No such file or directory
Dec 27 21:27:21 anime modprobe: FATAL: Could not load
/lib/modules/2.6.9-gentoo-r1/modules.dep: No such file or directory

There is one other error I see in the kernel log:

Dec 28 06:52:31 anime kernel: evbug.c: Event. Dev: macio/input0, Type:
18, Code: 2, Value: 750
Dec 28 06:52:31 anime kernel: evbug.c: Event. Dev: macio/input0, Type:
18, Code: 2, Value: 0
Dec 28 06:52:31 anime kernel: evbug.c: Event. Dev: macio/input0, Type:
18, Code: 1, Value: 0

Finally, the coup de grace. No time stamps since this is in dmesg, but
it is the last thing logged:

EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocks not in
datazone - block = 1327899396, count = 1
Aborting journal on device hda8.
ext3_abort called.
EXT3-fs error (device hda8): ext3_journal_start: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device hda8) in start_transaction: Journal has aborted
EXT3-fs error (device hda8) in start_transaction: Journal has aborted
EXT3-fs error (device hda8): ext3_free_blocks: Freeing blocks not in
datazone - block = 855704320, count = 1
ext3_reserve_inode_write: aborting transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device hda8) in
ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hda8) in ext3_truncate: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device hda8) in
ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hda8) in ext3_orphan_del: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device hda8) in
ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hda8) in ext3_delete_inode: Journal has aborted
__journal_remove_journal_head: freeing b_committed_data
EXT3-fs error (device hda8) in start_transaction: Journal has aborted

I ran a dd yesterday that copied the entire /dev/hda8 to /dev/null and
it completed with no errors. I also ran an fsck -c and there were no
bad blocks found.

Unless I can get some direction here, I am thinking of trying to
install YellowDog4 and see if it is more stable. Of course, if it does
not fail, then I know it was Gentoo. If it does, then it must be
hardware related.

Any help would be be appreciated,

Ben Ricker 


-- 
Ben Ricker
He's just this guy, you know?

--
[email protected] mailing list