Difference between revisions of "Fstab - Use SystemD automount/en"

Updating to match new version of source page
(Updating to match new version of source page)
 
(Updating to match new version of source page)
 
Line 20: Line 20:
Add the following to the beginning of the options section in your /etc/fstab, the numbers at the end are a time limit for how long it should try to make a connection before giving up & moving on:
Add the following to the beginning of the options section in your /etc/fstab, the numbers at the end are a time limit for how long it should try to make a connection before giving up & moving on:


  noauto,x-systemd.automount,x-systemd.device-timeout=10
  {{File|file=/etc/fstab|content=<pre>noauto,x-systemd.automount,x-systemd.device-timeout=10</pre>}}
 


After I added the above to the following line in my fstab:
After I added the above to the following line in my fstab:


  192.168.1.15:/media-2   /mnt/NAS-media-2 nfs   noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,hard,intr,noatime 0 0
  {{File|file=/etc/fstab|content=<pre>192.168.1.15:/media-2 /mnt/NAS-media-2 nfs noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,hard,intr,noatime 0 0</pre>}}
 


I could boot Manjaro whilst the ReadyNAS' Cat-6 network cable was unplugged, & there was NO noticeable delay. After the system was booted, I plugged the cable in & then called the NFS share /media-2 in Worker & it read the drive & listed the contents.
I could boot Manjaro whilst the ReadyNAS' Cat-6 network cable was unplugged, & there was NO noticeable delay. After the system was booted, I plugged the cable in & then called the NFS share /media-2 in Worker & it read the drive & listed the contents.
Line 33: Line 35:
If you have a very large /home & the boot process is held up when a scheduled fsck takes place (really not a big problem if you are using ext4), you can add the '''x-systemd.automount''' section to the options section of the line in your fstab for /home like so:
If you have a very large /home & the boot process is held up when a scheduled fsck takes place (really not a big problem if you are using ext4), you can add the '''x-systemd.automount''' section to the options section of the line in your fstab for /home like so:


  UUID=<id.number> /home noauto,x-systemd.automount,ext4 defaults 0 1
  {{File|file=/etc/fstab|content=<pre>UUID=<id.number> /home noauto,x-systemd.automount,ext4 defaults 0 1</pre>}}


This will allow services that do not depend on /home to start while /home is checked by fsck. Mounting /home when it is first accessed, the kernel will buffer all file access to /home until it is ready.}}
This will allow services that do not depend on /home to start while /home is checked by fsck. Mounting /home when it is first accessed, the kernel will buffer all file access to /home until it is ready.}}


[[Category:Contents Page{{#translation:}}]]
[[Category:Contents Page{{#translation:}}]]
8,560

edits