Re: reboot forcing a fsck

On Mon, Mar 18, 2024 at 2:08 PM Jim Pazarena <fquest@paz.bz> wrote:

> I have a server which seems to have a fs issue for my exim folder.
> an "ls -l" hangs. anything going near the exim folder hangs - for
> whatever reason.
>
> If I trigger a 'reboot', I assume the boot process will automatically
> enter a fsck as per the documentation.
>
> What is unclear is if the system will eventually g et to multi-user
> mode, or hang at a CLI question from the fsck?
>
> I have no hands or eyes available to be there. This is a bare metal
> chassis not a vm.
>
> Would appreciate learning the procedure which fsck uses during a boot.
> (beyond what the man fsck advises) which seems to exclude this question.
>
> Thanks
>
>
> --
> Jim Pazarena         fquest@paz.bz
> Haida Gwaii - British Columbia - Canad


Booting the system  will check that the root is marked CLEAN. If it is not
CLEAN, and it should not be in the case you describe, it will attempt an
fsck. If the fsck finds a problem, it will prompt you to select a shell.
'ENTER' runs the default, sh.

You can try something like 'fsck -y VOLUME'', but it really depends on the
file system settings. You can print these with 'tunefs -p VOLUME'. If
journaling is enabled, you should run an 'fsck -f VOLUME' to perform a full
fsck on the volume, ignoring the journal. Assuming journaling is enabled,
which is default, the journal may be bad, so only an fsck -f can repair hte
file system.
-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683