We are using nfs mounted filesystems with the amd.
If netfs daemon is restarted, the automounted filesystems
are not reachable anymore.
While stopping netfs, you get the message that it cannot
unmount the am-fs because are busy.
Trying to restart the amd do not help in any way. The only
solution is to log out, enter a console as root, unmount
(with 'umount' command) the am-fs, and restart the amd.
It would be nicer if netfs could handle these situations.
assigned to jbj
the netfs isn't a daemon ; it's simply something that mounts/unmounts
network filesystems. It shouldn't need 'restarted' per se. Why
are you doing a 'netfs restart'?
I discovered the bug by chance, while trying out things...
Running a 'netfs restart' or 'netfs stop' while someone is accessing
the am directories causes the amd to crash. I have seen it several
times, and every time I had to log out to restore it.
It's not a serious bug, because as you wrote there should be no need
to issue 'netfs restart'. But anyway, I still believe it's a bug! At
least, there should be no possibility to run 'netfs stop' if it's not
It might be that the bug is in amd. Namely, when you try to unmount an
am directory which is accessed, then the amd crashes.
assigned to nalin
Closing due to old age. Please reopen if you see the behavior in the latest