Theme name: oxygen-gtk Kernel version = 3.8.13-desktop-1.mga3 Distribution=Mageia release 3 (Official) for x86_64 CPU=Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz I configured a NFS share to be mounted automatically on my computer using Mageia Control Center (Access NFS Shared drives and directories). If the server is down (i.e. the NFS share is not available anymore) the configuration tool has two different behaviours: 1/ If the volumne was mounted when the NFS server goes down, and I open the configuration tool (to disable the mount), the tool crashes when opening. At the same time I noticed that running umount also doesn't work (umount hangs) and accessing the mounted folder with dolphing also ends up with a frozen dolphin. 2/ If the volume is not mounted at all (i.e. the NFS server was down when I started my machine) then I am able to open the configuration tool, but I can't see my volume there and have no option to disable or remove it (other than editing /etc/fstab directly). roti
Outside of the crash in the tool, I'd say this behavior is expected. If you have the share mounted when the server goes down, the mount is still there, it just won't respond. Most tools, including df and dolphin, or maybe this is the underlying NFS support blocking, have timeouts more suited to a network consisting of tin cans and string than ethernet cable or radio signals, which is why you see everything hang. You can get rid of the visible mount with umount -l, which will prevent the hangs. I'm a little surprised that the volume doesn't show up in the tool if it's in /etc/fstab, but that could be by design; the tool may be going by /etc/mtab rather than /etc/fstab. Try and get a stacktrace for the crash (run mcc from the command line in a terminal window and the stdout/stderr should show up there).
CC: (none) => ftg
For me diskdrake --nfs does not crash if the nfs server is unavailable, but it does hang. This is undesirable. At the moment I cannot see what causes it. As for your second point. I think the way it works is that the tool will show mounted or unmounted shares of entries in fstab, but only if it can resolve the host name given in fstab. So if fstab contains the zeroconf host name and the remote server is down then it will not resolve and will not display the entry. You could try proving this by changing the host name in fstab to an IP address. If this is the case, then I would be of the opinion that it is reasonable behaviour. If a host does not resolve, then it it is not going to conect either.
CC: (none) => derekjenn
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD