Ah, now I see. Yes, in that respect, that is, if you don't have a
chance to get /forcefsck written.
On 11/17/19 13:23, Dale wrote:
n952162 wrote:
How do you fix a broken filesystem, other than letting fsck have its way
with it?
The point is, don't touch it until you do. If you boot a system from
the hard drive, it has to be touched and you don't know what condition
it is in when your system has crashed in some way. If you boot some
other way and run fsck on it, then it is just like it was when your
system went down. It hasn't even been mounted read only at that point.
If you have data that can be replaced, it isn't a big deal. You can
restore from backups, fetch data again that was lost or whatever.
However, if you want to minimize that risk, don't touch the drive(s)
until fsck has done its job.
Dale
:-) :-)
