Quoting Jape Person <jap...@comcast.net>:
Not sure this will be at all helpful considering that the consensus
seems to be that fsck is probably not what you need right now. I
just wanted to be sure that you got some sort of answer regarding
the running of systemd-fsck.
You should be able to see the result of an fsck run with
$ cat /run/initramfs/fsck.log
I use
# tune2fs -c -1 /dev/sda1
to set the system to prevent a full fsck from running at boot time
and
# tune2fs -c 1 /dev/sda1
to cause the system to force a full fsck during the next boot.
Ah brilliant, thanks. I notice a few line like
/dev/vda1: Clearing orphaned inode 94755 (uid=106, gid=111,
mode=0100600, size=0)
/dev/vda1: Clearing orphaned inode 90459 (uid=106, gid=111,
mode=0100600, size=0)
but I really can't see this causing catastrophic server crashes if unfixed.
/Martin S
--
*************************************************************************
*** This address is for technical maillists only ***
*** Please use my primary mail address at the .org domain ***
*** for all other matters ***
*************************************************************************
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20150722032217.horde.ygrmaj13tjleehglec9z...@www.skjoldebrand.eu
