Guk-Bong, Kwon wrote:

why server hang or reset ?

I expect some warning/error message like "No space left on device"

and then I hope server is ok

NFS has always been awkward in limit conditions like this. People just
learn to stay away from such boundary conditions if they want reliable
servers, for this and other good reasons already mentioned.

2012/8/7 Burbidge, Simon A [off-list ref]:

quoted

Hi Kwon,
I'd suggest that the asynchronous nature of NFS means that you've got all the nfs threads on the client waiting on a response from
the NFS server. The server is in trouble because you've no free blocks and nfs has also filled up your buffer cache with data blocks and the
nfs server threads have blocked waiting on this.
While xfs might still be responsive on the server, it may very slow as it scrabbles around for the last free block.

In my experience, in any situation with NFS where the server filesystem fills up completely, you'll get a hang.
Sometimes you can free space by removing files, sometimes the server is unresponsive and you have to reset.

What Simon said.

Cheers, Dave

PS  It would be lovely if you could trim your posts :)  Thanks.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs