[lkml]   [2001]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Journaling: Surviving or allowing unclean shutdown?

On Fri, Jan 05, 2001 at 12:46:19PM +0000, Alan Cox wrote:
> > recovery. Because the ext3 journal is just a series of data blocks to
> > be copied into the filesystem (rather than "actions" to be done), it
> > doesn't matter how many times it is done. The recovery flags are not
> > reset until after the journal replay is completed.
> Which means an ext3 volume cannot be recovered on a hard disk error.

Depends on the error. If the disk has gone hard-readonly, then we
need to recover in core, and that's something which is not yet
implemented but is a known todo item. Otherwise, it's not worse than
an error on ext2: you don't have a guaranteed safe state to return to
so you fall back to recovering what you can from the journal and then
running an e2fsck pass. e2fsck groks the journal already.

And yes, a badly faulty drive can mess this up, but it can mess it for
ext2 just as badly.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.113 / U:0.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site