Messages in this thread | | | Date | Fri, 23 Jan 2004 09:22:25 +0100 | From | Jan Dittmer <> | Subject | Re: ext3 on raid5 failure |
| |
Theodore Ts'o wrote: > On Sun, Jan 18, 2004 at 10:02:32AM -0800, Mike Fedyk wrote: > >>On Sun, Jan 18, 2004 at 11:27:54AM +0100, Jan Dittmer wrote: >> >>>EXT3-fs error (device dm-1): ext3_readdir: bad entry in directory >>>#9783034: rec_len % 4 != 0 - offset=0, inode=1846971784, rec_len=33046, >>>name_len=154 >>>Aborting journal on device dm-1. >>>ext3_abort called. >>>EXT3-fs abort (device dm-1): ext3_journal_start: Detected aborted journal >>>Remounting filesystem read-only >> >>Run fsck on the filesystem. > > > Jan, what distribution are you running? The superblock *should* have > been marked "filesystems has errors", and so fsck should have been > forced when you rebooted. Did fsck in fact run, and if so, did it > detect and fix any problems? > > - Ted
Okay, I fscked all filesystems in single user mode, thereby fscked up my root filesystem, though I didn't even check it - so I restored it from backup (grub wouldn't even load anymore). After 2 days in my freshly setup debian (2.6.1-bk6), same error. But this time at least I know it's because I tried to delete those files in the lost+found directory... So, how do I delete these and why did fsck fail? It's pretty annoying to reboot because of this. It would be nice to just being able to remount,rw the partition.
Thanks,
Jan
EXT3-fs error (device dm-2): ext3_readdir: directory #16370 contains a hole at offset 8192 Aborting journal on device dm-2. EXT3-fs error (device dm-2): ext3_readdir: directory #16370 contains a hole at offset 24576 ext3_abort called. EXT3-fs abort (device dm-2): ext3_journal_start: Detected aborted journal Remounting filesystem read-only [unhandled content-type:application/pgp-signature] | |