Hi, On Wed, Mar 27, 2002 at 05:25:43PM +1030, Tony Clark wrote: > I suspect I may need to retract that last one, as I just forced a fatal > error on EXT2 as well... I'd appreciate any thoughts people have in > terms of locating the fault, although I suspect it's in the raid. > > Mar 27 17:28:15 r5 kernel: journal_bmap: journal block not found at > > offset 1607 on sd(8,17) > > Mar 27 17:28:15 r5 kernel: Aborting journal on device sd(8,17). That's a fatal error in which one of the journal's key data structures has been corrupted. It's a completely readonly data structure, which tells the filesystem where the journal is on disk. If you're getting an error there, it's a fair bet that the problem is the underlying data corruption, not ext3 itself. Cheers, Stephen
