Messages in this thread | | | From | Dawson Engler <> | Subject | Re: [MC] Re: [CHECKER] e2fsck writes out blocks out of order, | Date | Tue, 11 May 2004 23:21:48 -0700 (PDT) |
| |
> > On Tue, 11 May 2004, Junfeng Yang wrote: > > > Hi, > > > > We got a warning that the filesystem was in a inconsistent state when: > > 1. created a crashed disk image > > 2. ran fsck over the image and then crash fsck at certain point > > 3. re-ran fsck. > > Question? Is fsck specified to be able to be crashed? I'm not > sure you could ever make a repair-tool that could do that unless > there was some "guaranteed to save device" on an independent power > source during the repair. Fsck can't commit partial fixes of some > stuff because it would leave the file-system in an unrecoverable > state. It needs to complete.
To the extent that it is simply replaying records in a journal, it should be able to crash at arbitrary points before commit and then restart without fuss. That's one of the motivations for using logging in a file system ;-) - 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/
| |