--- Comment #14 from Scott Couston <scott(a)aphofis.com> 2012-02-06 10:17:57 UTC ---
The other issues I have been testing of late are also 100% reproducible and
relate to ANY situation where both or only the NFS Server PC and/or the NFS
Client PC have not been totally shutdown when S2RAM and/or S2Disk has been
Despite the NFS Server being re-established before its NFS Clients, no NFS
Server/Client relationship is ever remounted and fails completely.
In this situation the NFS Client will hang at sm-notify until the same huge
time-out of in excess of 5 minutes has elapsed. In this situation where the PC
is left to time-out NO NFS Client services are EVER reinstated. This is as much
the fault of the NFS Server as well al its NFS Client. Where both Server and
Client are both halted by S2RAM Or S2Disk and then resumed, NO NFS Services
what-so-ever are ever re-established.
If you need more log data regarding this test please be specific.
AJ........Given this new test where NO NFS Services what-so-ever are recreated
please reassess the assigned priority...This goes from bad to worse
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.