Why does the desktop freeze whenever an NFS share fails? I have set all NFS mounts to soft,intr and yet, if I forget to unmount a share before taking down the NFS server, my desktop freezes.

On 08/16/15 06:50, Patrick O'Callaghan wrote: > On Sat, 2015-08-15 at 15:16 -0700, Emmett Culley wrote: > > Why does the desktop freeze whenever an NFS share fails? I have > > set > > all NFS mounts to soft,intr and yet, if I forget to unmount a > > share > > before taking down the NFS server, my desktop freezes. > Maybe for the same reason my local NFS-mounted NAS starts up any > time I > open Dolphin, even when I'm just looking at a local directory. > Something in KDE wants all possible filesystems available before it > allows you to look at anything, or at least it seems that way. I've > never bothered trying to pin it down. > I am not seeing any desktop "freeze". I see that dolphin will get "stuck" when I open it up since 2 NFS mounts are at my $HOME location. Also, ls will freeze up. I didn't uninstall, but I did tell "tracker" not to index anything. I'm sure someone finds "tracker" useful. :-)

Emmett Culley wrote: > Why does the desktop freeze whenever an NFS share fails? I have set all > NFS mounts to soft,intr and yet, if I forget to unmount a share before > taking down the NFS server, my desktop freezes. > > Luckily I have Yakauke running, so I can at least get to a console. But > of course the NFS mount cannot be umounted if it doesn't respond. > > Also I assumed the setting shares to intr, soft would prevent other > software from hanging if the share stops responding. Is that not so? Or > is there another setting I am not aware of? > > Any ideas how to prevent this from happening? It not *that* different to when a (mounted) disk stops working. I'd recommend focusing on simply avoiding that situation.

On Sun, 2015-08-16 at 14:11 -0400, Adam Batkin wrote: > On 08/16/2015 07:01 AM, Rex Dieter wrote: >> Emmett Culley wrote: >> >>> Why does the desktop freeze whenever an NFS share fails? I have >>> set all >>> NFS mounts to soft,intr and yet, if I forget to unmount a share >>> before >>> taking down the NFS server, my desktop freezes. >>> >>> Luckily I have Yakauke running, so I can at least get to a >>> console. But >>> of course the NFS mount cannot be umounted if it doesn't respond. >>> >>> Also I assumed the setting shares to intr, soft would prevent >>> other >>> software from hanging if the share stops responding. Is that not >>> so? Or >>> is there another setting I am not aware of? >>> >>> Any ideas how to prevent this from happening? >> >> >> It not *that* different to when a (mounted) disk stops working. >> I'd >> recommend focusing on simply avoiding that situation. > > I assume that you were referring to local (physical) disks. > > Regardless, I disagree: Failure happens and software should at least > *attempt* to be resilient. > > If I'm asking Konqueror or Dolphin to access a broken mount (local or > network) then I understand if it hangs (though that could be avoided > too, even if it just displays a "loading" indicator since it > obviously > can't get any further). > > But for general operations I would expect that nothing should hang. > This > is a solvable problem, and suggesting that people should avoid hung > mounts isn't helpful given that usually (this particular situation > excepted) they are totally unavoidable. A hung desktop is never > acceptable. +1 poc _______________________________________________ kde mailing list kde(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org

Emmett Culley wrote: > Why does the desktop freeze whenever an NFS share fails? I have set all > NFS mounts to soft,intr and yet, if I forget to unmount a share before > taking down the NFS server, my desktop freezes. > > Luckily I have Yakauke running, so I can at least get to a console. But > of course the NFS mount cannot be umounted if it doesn't respond. > > Also I assumed the setting shares to intr, soft would prevent other > software from hanging if the share stops responding. Is that not so? Or > is there another setting I am not aware of? > > Any ideas how to prevent this from happening? It not *that* different to when a (mounted) disk stops working. I'd recommend focusing on simply avoiding that situation.

-- rex _______________________________________________ kde mailing list kde(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org

On 15/08/15 23:16, Emmett Culley wrote: > Why does the desktop freeze whenever an NFS share fails? I have set all NFS mounts to soft,intr and yet, if I forget to unmount a share before taking down the NFS server, my desktop freezes. > > Luckily I have Yakauke running, so I can at least get to a console. But of course the NFS mount cannot be umounted if it doesn't respond. > > Also I assumed the setting shares to intr, soft would prevent other software from hanging if the share stops responding. Is that not so? Or is there another setting I am not aware of? > > Any ideas how to prevent this from happening? > > Emmett Emmette I asked a similar question on 11 July in this list, to which there was no real answer. The issue has been in KDE for many years (although I don't know if its had the same cause all along). If you google you'll find lots of people asking about this. We have quite a lot of cross-mounted disks so I always have to be careful when rebooting an nfs server particularly as systemd often seems to find some reason to wait 3 mins in the shutdown phase while a stop job is running. Roderick _______________________________________________ kde mailing list kde(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org

On Tuesday 18 August 2015 06:42:11 Emmett Culley wrote: > This is becoming a pretty serious issue for us. We have more that 15 local > servers (both hardware and VM's) many of which are development machines. > Which means they are often rebooted or otherwise taken off-line. > > When that happens to a machine that someone has mounted an NFS share from, > those with that mount get locked up. Just my 2 penny worth, but... I understand that this is annoying and would be good to have a solution on the system/KDE level, so NFS mounts are not locking system when they disappear. It however rings in my head as to why in earth one would put an NFS service on a servers that are development / rebootable .... Logically, I would look at creating a single NFS server, and making your local machines to use that for any file sharing purposes.. _______________________________________________ kde mailing list kde(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org

On Wed, 2015-08-19 at 12:20 -0700, Emmett Culley wrote: > The issue here is why does KDE stop, like a single threaded windows > 3.1, when an NFS share disappears? Very well put.

poc _______________________________________________ kde mailing list kde(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org

These servers are all development servers, and having NFS access allows our development IDE's to have direct access to the code under development. So there is a very good use case for having "unstable" NFS servers on the network.