NFS sync vs. async mounts (was Re: [opensuse] OpenSuse 10.2 - Fortran compilation very slow through NFS network with a 64bit server and 32bit clients.)



Randall R Schulz wrote:
In particular, you can get notification of an error (e.g., "disk full") on the reply to a request much later than that of the request which actually encountered the error. Software with complex ordering and error sensitive behavior can be seriously undermined by asynchronous NFS. E.g. one of the most subtle problems I ever debugged was corruption in Berkeley DB files when the aforementioned disk-full condition occurred on a file system being accessed by the BDB code over asynchronous NFS.
---
Ug! Running a 'db' over NFS? That's sounds
ugly -- especially for performance. I don't think NFS was
designed for such -- since to get any performance out of
NFS, the defaults are to cache information on the client.
That's not acceptable with a heavily shared database.
Even on local disks, I don't think anything but 'synchronous'
is recommended for critical database applications.

I suppose my assumption is that if someone had a
critical business application that they needed to be networked,
they'd more likely be using one of the Suse-Business editions
and not asking about performance questions on the open-suse
list...:-) But that is an assumption...:-) For "Fortran"
compilations, (development work), I'd strongly recommend
async operation as preferable for performance reasons. But
to each their own...:-)

Linda
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx



Relevant Pages

  • [GIT] NFS client updates for 2.6.22...
    ... commit a19b89cad51b6f0da8f4bafdfdcfb10264cbcdea ... should remove any cached ACL so that any subsequent request for the ACL ... NFS: Fix directory caching problem - with test case and patch. ...
    (Linux-Kernel)
  • NFS negative dentry caching problem in 2.4.21, and patch
    ... Below is a description of the problem and a suggested patch. ... Hat support request, so when it says "RHEL3", think "Linux 2.4.21". ... We have a big problem with how the NFS client code in RHEL3 ... from an NFS server (doesn't matter what kind, ...
    (Linux-Kernel)
  • NFS client side bug fixes that probably apply to FBsd-4 and 5.
    ... Fix a bunch of NFS races. ... likely to occur now due to the additional thread switching that DragonFly ... processing (e.g. transmission) of the request. ...
    (freebsd-hackers)
  • Re: NFS Still broken in 2.6.x?
    ... I'm running into a bit of trouble with NFS on 2.6. ... The patch below should fix this problem. ... Subject: Readahead algorithm problems again... ... 32k max, 4k request ...
    (Linux-Kernel)
  • Re: Compressing file system, NFS
    ... > not given a request of dealing with an entire file, ... say redoing nullfs to slip in compression. ... > supports NFS, and it supports very large files and disk farms. ... Novell NetWare is no option for me. ...
    (comp.unix.bsd.freebsd.misc)