Hi. On Wed, 30 Dec 2020 23:28:11 +0800 Ed Greshko wrote:
> On 30/12/2020 22:09, François Patte wrote: >> 192.168.1.16:/data /home/patte/data nfs >> noauto,rw,user,nofail,x-systemd.automount,x-systemd.mount-timeout=30 0 0 >> It works. If the server is down, no problem, the boot of the computer is OK. >> But if the server gets down while the computer is working, this turns in an >> awful way: everything on the computer becomes very slow, opening a file >> manager takes ages, the ls command does no work and it is impossible to >> unmount the directory on which the server is mounted. >> Did I forgot an option in the fstab? Is there a way to solve this problem >> without shuting down the computer (which also takes ages...). > Try adding "soft" to the options. That will help yes, but you will still have timeouts. A better choice would be to do the mount not directly under your homedir or totally elsewhere, for example: /home/patte/net/data /data Do not put a symlink ~/data pointing to the mountpoint: you will have the same problem: 'ls --color=auto" and the file managers (as far as I know) follow symlinks. gvfsd (the gnome virtual filesystem) used to do its mount under ~/.gfvs, but do it now under /run/user/$UID/gvfs Using autofs instead of systemd-automount would have the advantage to unmount automatically after some delay. You can perhaps force the umount with: sudo umount --lazy /home/patte/data -- francis _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
