Quote:
Originally Posted by map7
I understand that to fix problems with fsck you must first unmount that filesystem. If you look at post #4 in this thread, you will see I have tried running fsck in single user mode with the filesystems unmounted.
|
But, all the bits you posted showing fsck running, show "NO WRITE ACCESS".
Quote:
Are you guys saying that I should ignore the errors I get when running fsck on a mounted filesystem because fsck is not supposed to be run this way? I know fsck will not fix errors on a live system, but does it report invalid problems with the filesystems if they are mounted?
|
If softupdates are enabled on the filesystem, then yes, the results you get from running fsck on a mounted filesystem will be undefined. Softupdates changes the way files are deleted, and space reclaimed.