Comment 13 for bug 42121

I have also observed this bug a few times when trying to hibernate with a share that has dropped without being unmounted first. Because of the long delay during whatever process is happening to generate the error messages, hibernate fails due to processes not shutting down. (Hibernate will work if tried again if the dead share is unmounted, so it does not have any lasting effect.) I also occasionally see this message in my log files, possibly because I run scripts to dynamically load and unload shares on my network. Any solution to this bug requires significantly more than a revision to the shutdown scripts to be a true resolution.