Simply put, a "cat /dev/zero > [home on nfs]/tmpfile" on a SRS almost
stalls the server. (ls takes >1s!)
Are we the only ones experiencing this?
Our users tend to work with very large files, so reading or writing a
couple of GB at a time does happen frequently enough to be a real problem.
We have a fairly simple setup: A single Solaris/ZFS based NFS server
with loads of disks and two Linux based SRS servers mounting /home.
Saturating the servers links using other clients does not cause any
problems, but once one client's link is full, all other processes on
that client wait ages on i/o.
Considering the number of users some of you put on one box, this issue
must have come up before. What am I doing wrong? How do you all solve
this? Or, does anyone have an idea how to fix it?
Does using an automounter help? Or NFS4? Or a different NFS server?
Elmar
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
