ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device hda3) in start_transaction: Journal has aborted EXT3-fs error (device hda3) in start_transaction: Journal has aborted [...] I hit a similar problem yesterday, but lost some details so I couldn't make a proper bug report. However, it did mean that the partition got fully fscked, so I think these errors are ext3 getting confused all by itself, rather than it complaining about an already-corrupt filesystem. There's no sign of any hardware problems with the disk or controller in the logs. No extra ext3 parameters were set when mounting this partition originally. Going back through the logs, there are also these worrying messages (from the previous crash): attempt to access beyond end of device hda3: rw=0, want=24855217912, limit=143235540 attempt to access beyond end of device hda3: rw=0, want=7590624504, limit=143235540 attempt to access beyond end of device hda3: rw=0, want=17158939432, limit=143235540 attempt to access beyond end of device hda3: rw=0, want=32230066456, limit=143235540 Is there any other information I can supply to help track down what's going wrong? Ben -- Ben Mansell, <ben@xxxxxxxx> Zeus Technology Ltd Download the world's fastest webserver! Universally Serving the Net T:+44(0)1223 525000 F:+44(0)1223 525100 http://www.zeus.com Zeus House, Cowley Road, Cambridge, CB4 0ZT, ENGLAND _______________________________________________ Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
