1 |
n952162 wrote: |
2 |
> How do you fix a broken filesystem, other than letting fsck have its way |
3 |
> with it? |
4 |
|
5 |
The point is, don't touch it until you do. If you boot a system from |
6 |
the hard drive, it has to be touched and you don't know what condition |
7 |
it is in when your system has crashed in some way. If you boot some |
8 |
other way and run fsck on it, then it is just like it was when your |
9 |
system went down. It hasn't even been mounted read only at that point. |
10 |
If you have data that can be replaced, it isn't a big deal. You can |
11 |
restore from backups, fetch data again that was lost or whatever. |
12 |
However, if you want to minimize that risk, don't touch the drive(s) |
13 |
until fsck has done its job. |
14 |
|
15 |
Dale |
16 |
|
17 |
:-) :-) |