On 2022-04-27 22:30, Per Inge Oestmoen wrote:
Carlos E. R. wrote:
On 2022-04-27 16:31, Per Inge Oestmoen wrote:
Carlos E. R. wrote:
On the other hand, this should not be done on a mounted filesystem
This was done on a data backup disk, not on my system disk.
Yes, but that is irrelevant. You must not do an fsck on a mounted filesystem.
Ouch, how can I ascertain whether or not my file system has become corrupt? Unmount it and then run fsck, of course.
Yes. But it is very rare for a filesystem to become corrupt while mounted. It could happen if the machine is hibernated, then you remove a disk and put it in another machine or system.
By the way: How do I do it if I want to run fsck on my system disk? From a USB stick?
Yes. Or just reboot. Usually there is a quick check at boot. There was a way to force an fsck on boot by creating a file on / of a certain name; I have forgotten the name, and I don't know if systemd honours this. Google says it is "/forcefsck". You can try if you are curious, and then you tell us :-) # touch /forcefsck -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)