On Tue Mar 25, 2003 at 03:54:58AM -0800, Terry Lambert wrote: > Alexander Langer wrote: > > Thus spake Terry Lambert ([EMAIL PROTECTED]): > > > Disable write caching on your ATA drive. You should be able to > > > "safely" reset after that. > > > > Good idea, thanks. Nevertheless: I don't think the system should > > panic on background fsck's, while a manual fsck works. > > A manual fsck can deal with corrupt data. > > A background fsck can only deal with invalid cylinder group > bitmaps, and operates on a snapshot. > > For a background fsck to be feasible, the FS has to be in a > self-consistent state already, which it wasn't. > > When you killed the power on your system and reset it, you > lost the cached data sitting in the ATA disk. This is due > to the fact that the ATA disk lied, and claimed that it had > committed some writes to stable storage, when in fact it had > only copied them to the disk cache. As a result, when the > device reset happened, you lost some writes which were in > progress. Therefore you disk image was corrupt, and so your > FS was *not* in a self-consistent state.
Shouldn't fsck run in the foreground for disks setup with WC? That
would be a quick hack solving this issue altogether.
A.
--
Conformity-the natural instinct to passively yield to that vague something
recognized as authority.
- Mark Twain
pgp00000.pgp
Description: PGP signature
