Messages in this thread | | | Date | Mon, 19 Jan 2004 10:30:05 -0500 | From | Theodore Ts'o <> | Subject | Re: ext3 on raid5 failure |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |