At 04:00 AM 5/20/2008, Chris Fanning wrote:
>However it does show up in /proc/mounts
>nfs_home_server:/home /home nfs
>rw,vers=3,rsize=32768,wsize=23768,hard,nointr,proto=tcp,timeo=600,retr
>ans=2,sec=sys,addr=192.168.2.2
>0 0
Is that a transcription typo - "23768"?
As Trond mentioned though - NFS can't cause server corruption.
If server "async" changes this, there's a deeper root cause.
Tom.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that [email protected] is being discontinued.
Please subscribe to [email protected] instead.
http://vger.kernel.org/vger-lists.html#linux-nfs