You are not logged in.
I have set up a NFS mount in my fstab to unmount when I'm not accessing it with these settings
192.168.0.142:/mnt/tank/media/Downloads /run/media/Downloads nfs noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=1min,user 0 0
I want to set it so that it unmounts the share and leaves it unmounted until I try to access it so that it's not constantly using resources on the server .
Even when not in use for some reason it keeps trying to mount. On the server you can see that after a minute it tries to unmount the server but then instantly remounts even though I'm not accessing it.
Jan 24 12:14:08 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:15:08 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:15:08 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:16:09 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:16:09 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:17:10 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:17:10 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:18:10 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:18:10 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:19:11 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:19:11 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:23:05 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:23:05 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:24:06 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:24:06 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:25:06 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:25:06 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:26:07 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:26:07 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:27:08 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:27:08 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:28:28 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:28:28 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:29:29 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:29:29 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:30:30 Lilan mountd[2171]: umount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
Jan 24 12:30:30 Lilan mountd[2171]: mount request succeeded from 192.168.0.2 for /mnt/tank/media/Downloads
I'm not trying to access to share in any way I can think of so I don't know why it would keep trying to remount it. Is there something I need to set so that it won't keep trying to remount it?
Offline
I think you should be using autofs for this - https://wiki.archlinux.org/index.php/Autofs
Offline
@STREBLO
Are you sure some service or DE feature isn't trying to access the directory? Maybe see what happens without X running, particularly if you're running KDE or Gnome.
@paulkerry
AFAIK, systemd's automount serves the same purpose (more or less) as autofs. Is there a reason you think it would be better for OP?
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
@STREBLO
Are you sure some service or DE feature isn't trying to access the directory? Maybe see what happens without X running, particularly if you're running KDE or Gnome.
@paulkerry
AFAIK, systemd's automount serves the same purpose (more or less) as autofs. Is there a reason you think it would be better for OP?
I am running KDE but other than having it mounted nothing I can think of. Anyway i'll give that a try.
Offline
i have the same issue here. Really annoying is that everytime i open the devicemanager plasmashell freeze.
bugreport here:
https://bugs.kde.org/show_bug.cgi?id=355258
perhaps this is also important:
https://github.com/systemd/systemd/issues/2181
seems there's something to fix
Offline
@paulkerry
AFAIK, systemd's automount serves the same purpose (more or less) as autofs. Is there a reason you think it would be better for OP?
None apart from checking if autofs works and automount doesn't.
Offline