Arch Linux

battlepanic

Member

Registered: 2009-08-22

Posts: 76

systemd failing to mount a network share

I just installed systemd and I'm having some problems getting it to reliably mount the network shares I have listed in /etc/fstab.  In case it is relevant, I should note that I have opted to install systemd alongside the usual initscripts.  I've created two different Grub menu entries to select between the two systems during boot.

The relevant fstab entries are as follows:

//192.168.1.54/MP3z /mnt/MP3z/ cifs _netdev,password=foo,uid=foo,gid=foo,file_mode=0644,dir_mode=0755 0 0
//192.168.1.100/share /mnt/share/ cifs _netdev,password=foo,uid=foo,gid=foo,file_mode=0644,dir_mode=0755 0 0
//192.168.1.100/docs /mnt/docs/ cifs _netdev,password=foo,uid=foo,gid=foo,file_mode=0644,dir_mode=0755 0 0

This is what I've observed with respect to mount failures:

• The share at 192.168.1.54 mounts every time without fail.

• Usually, one of the other two shares at 192.168.1.100 will fail to mount while the second share at the same ip address will succeed.  Which of the two that fails is apparently random.

• Only very occasionally will both shares at 192.168.1.100 mount successfully.

• So far, I have never seen both of these shares fail to mount on the same test run.

• I have tried changing the order of the fstab entries but it doesn't seem to affect things.

I've tried adding the "noauto" and "x-systemd.automount" options to my fstab entries.  This seems to make things work although with this setup I think the shares are mounted the first time they are browsed, not during starup.  With these mount options set, the system hangs on shutdown with either the messsage "Unset automount mnt-share.automount" or "Unset automout mnt-docs.automount".

I thought perhaps that this is happening because my network connection isn't being started in time to mount the shares correctly.  Though, I thought systemd handled these sorts of dependencies without any explicit configuration required.  Perhaps this has something to do with the two shares being on the same host (192.168.1.100)?  I don't have any problems with the third share at 192.168.1.54.

Can anyone shed some light?

Last edited by battlepanic (2012-08-15 19:28:05)