The synchronous writes on NFS V2 "require" that the data be safely on disk
before a reply is made. Even the V3 clients with unstable writes should?
must? had better do a COMMIT at close time to catch any errors, including
out-of-space errors the biods haven't reported yet.
Therefore, NFS writes are limited to disk speed, and V2 writes suffer from
several seeks per write unless assisted by write gathering, NVRAM, and
related whatnot.
I would not be surprised if most people on this list don't have an 18
disk array to help spred the load.
BTW, given your hardware, 1963 KB/sec is not terribly exciting. V3 should
easily see that with a single disk. What do you get from some other V3
client? Expect that Trond will be pestering you for data ASAP.
-Ric Werme
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/