On 12/3/18 9:50 PM, Tim via users wrote: > Allegedly, on or about 30 November 2018, Patrick O'Callaghan sent: >> When I tried to list a directory on the system it didn't respond, but >> doing an ssh to the box spins up the disks and lets me log in. So >> I've no idea what exactly automount is supposed to be doing. > I have a similar issue. If the NAS has gone to sleep, it's very hard > to wake up. It takes so long, that the autofs thing that Fedora does > gives up and refuses to try again. If I open up the webserver > interface to the NAS, rummage around the contents a bit, the drive > wakes up, and then NFS automounts work fine. > > Another NAS is quicker at coming to life, and doesn't have that > problem. > > If something has got its hooks into trying to use autofs (like a > Nautilus browser window, or an application's file requester), this can > really jam up the works on an automount that's not mounting. > > I'd like to know if I can tweak a timeout for autofs, I didn't used to > have this problem. > Have a look at x-systemd.device-timeout and x-systemd.mount-timeout in "man systemd.mount". I've not had problems since my NFS server is pretty darn quick even if the drives have spun down. So, I've not had to research this. And, since everything works well for me, I've no way to really test. -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
