severity 757544 normal
thanks
I agree this should be fixed, but what e2fsck was doing was at best a
contributory factor. #1, the user pulled the disk while it was still
being active. And #2, e2fsck is writing back the updated superblock
and block group descriptors. If any of these changes had been lost, a
second run of e2fsck should have fixed them.
The fact that the disk did additional damage on a power fail which
caused the data loss is the disk's problem, not e2fsck's.
I'll fix this, but even so, unexpected power lost should have caused
anything other than a need to rerun e2fsck. I suspect the fault of
the hardware.
- Ted
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
