You are not logged in.
Pages: 1
I have an encrypted drive that I mount as home on login using the pam method (the only difference is that I also have x-systemd.automount as an option, as I think that page used to recommend that but does not anymore). Everything works fine and has been for quite a while now. But I was wondering whether this drive is ever fscked. Before I encrypted home, after however many boots is the default, fsck would run on the home partition, and because it is pretty big, it would take a while. That never seems to happen anymore. I thought I had read that x-systemd.automount would also run fsck, but I'm guessing it's not.
So my questions are: 1) With this setup is fsck being run? 2) If so, when is it happening, as I never get the delay that used to happen when it was run, and 3) If it is not being run, should I do something to make sure that fsck is occasionally run on this encrypted drive?
Last edited by slamhound (2019-09-28 22:59:24)
Offline
My guess is that it is run, but you could check if it is working correctly:
journalctl -u systemd-fsck*Offline
Ah, great, thanks! Yup, looks like it is.
Offline
Pages: 1