On Tue, 14 May 2002 11:16:26 +0100 "Stephen C. Tweedie" <sct@redhat.com> wrote: > > JFS: Failed to read block at offset 813 > > JFS: IO error -5 recovering block 813 in log > > e2fsck: Input/output error while recovering ext3 journal of backup > > > > What should my next step be? > > Looks like you've got a bad block in the journal itself --- that's bad > news. We should really try to recover from this in e2fsck, but > there's really nothing that the kernel can do --- an unrecoverable > journal means that a full fsck is absolutely necessary. > > For now, try removing the journal and fsck'ing: > > tune2fs -O ^has_journal Thanks for your rapid response. >tune2fs -O ^has_journal /dev/sdb5 gives tune2fs 1.24a (02-Sep-2001) The needs_recovery flag is set. Please run e2fsck before clearing the has_journal flag. So, then:- e2fsck /dev/sdb5 e2fsck 1.24a (02-Sep-2001) backup: recovering journal backup: recovering journal backup: recovering journal backup: recovering journal backup: recovering journal backup: recovering journal .... This seems to have gone into a loop. - Richard -- Richard Kimber Political Science Resources http://www.psr.keele.ac.uk/ UK-Euro FAQ http://www.psr.keele.ac.uk/docs/efaq.htm
