You are not logged in.
How do I say it to check only after crashes (bad unmounts and so on..) and just mount without checks otherwise?
I use the classic /etc/fstab layout:
/dev/drive/root / ext4 rw,relatime 0 1
/dev/drive/boot /boot ext4 rw,relatime,noexec 0 2
/dev/drive/swap none swap defaults 0 0
/dev/drive/var /var ext4 rw,relatime,nodev,noexec,nosuid 0 2
/dev/drive/home /home ext4 rw,relatime 0 2Here is some info from systemd's journal:
дек. 08 22:43:20 localhost systemd[1]: Found device /dev/drive/var.
дек. 08 22:43:21 localhost systemd-fsck[124]: /dev/mapper/drive-root: clean, 56204/2621440 files, 523339/10485760 blocks
дек. 08 22:43:21 localhost systemd[1]: Started File System Check on Root Device.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/var...
дек. 08 22:43:21 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/swap.
дек. 08 22:43:21 localhost systemd[1]: Activating swap /dev/drive/swap...
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/boot.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/boot...
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/home.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/home...
дек. 08 22:43:21 localhost systemd-fsck[252]: /dev/mapper/drive-var: clean, 2007/262144 files, 463082/1048576 blocks
дек. 08 22:43:22 localhost systemd[1]: Started Remount Root and Kernel File Systems.
дек. 08 22:43:22 localhost systemd[1]: Starting Local File Systems (Pre).
дек. 08 22:43:22 localhost systemd[1]: Reached target Local File Systems (Pre).
дек. 08 22:43:22 localhost systemd[1]: Mounting /var...
дек. 08 22:43:22 localhost systemd-fsck[257]: /dev/mapper/drive-boot: clean, 313/65536 files, 33914/262144 blocks
дек. 08 22:43:22 localhost systemd[1]: Mounted /var.
дек. 08 22:43:22 localhost systemd-fsck[262]: /dev/mapper/drive-home: clean, 5080/16375808 files, 2332630/65492992 blocks
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/boot.
дек. 08 22:43:22 localhost systemd[1]: Mounting /boot...
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/home.
дек. 08 22:43:22 localhost systemd[1]: Mounting /home...
дек. 08 22:43:22 localhost systemd[1]: Mounted /boot.
дек. 08 22:43:23 localhost systemd[1]: Mounted /home.
дек. 08 22:43:23 localhost systemd[1]: Starting Local File Systems.
дек. 08 22:43:23 localhost systemd[1]: Reached target Local File Systems.These filesystem checks seem to add huge delay to boot time. But I don't want this delay!
Last edited by eruditorum (2012-12-10 19:26:54)
Offline
These are the same checks that have always occurred. Notice that /home is mounted within the same second timestamp that it's fsck'd. Same goes for /boot, and /var is probably under a second as well. If you're seeing delays, go look elsewhere.
Offline
Hmmmm... Wonder what the solution was? ![]()
Registered Linux user #436067
Offline
These are the same checks that have always occurred.
But I want to remove them!
Notice that /home is mounted within the same second timestamp that it's fsck'd. Same goes for /boot, and /var is probably under a second as well. If you're seeing delays, go look elsewhere.
I think filesystem checks add delays (about one second for each logical volume or so), also as you know systemd is doing everything in parallel it can at the given moment of time, for example I can say you that water has already boiled, while it is still going to boil but you don't know it:
/:
дек. 08 22:43:19 localhost systemd[1]: Starting File System Check on Root Device...
дек. 08 22:43:21 localhost systemd-fsck[124]: /dev/mapper/drive-root: clean, 56204/2621440 files, 523339/10485760 blocks
дек. 08 22:43:21 localhost systemd[1]: Started File System Check on Root Device.
дек. 08 22:43:21 localhost systemd[1]: Starting Remount Root and Kernel File Systems.../var:
дек. 08 22:43:20 localhost systemd[1]: Found device /dev/drive/var.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/var...
дек. 08 22:43:21 localhost systemd-fsck[252]: /dev/mapper/drive-var: clean, 2007/262144 files, 463082/1048576 blocks
дек. 08 22:43:21 localhost systemd[1]: Started File System Check on /dev/drive/var.
дек. 08 22:43:22 localhost systemd[1]: Mounting /var...
дек. 08 22:43:22 localhost systemd[1]: Mounted /var./boot:
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/boot.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/boot...
дек. 08 22:43:22 localhost systemd-fsck[257]: /dev/mapper/drive-boot: clean, 313/65536 files, 33914/262144 blocks
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/boot.
дек. 08 22:43:22 localhost systemd[1]: Mounting /boot...
дек. 08 22:43:22 localhost systemd[1]: Mounted /boot./home:
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/home.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/home...
дек. 08 22:43:22 localhost systemd-fsck[262]: /dev/mapper/drive-home: clean, 5080/16375808 files, 2332630/65492992 blocks
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/home.
дек. 08 22:43:22 localhost systemd[1]: Mounting /home...
дек. 08 22:43:23 localhost systemd[1]: Mounted /home.Last edited by eruditorum (2012-12-09 13:20:15)
Offline
falconindy wrote:These are the same checks that have always occurred.
But I want to remove them!
If you so desperately want to remove these checks, then you can disable them via the same mechanism that's always been available to you in fstab. But really, you don't want to disable them.
Offline