All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wendy Cheng <wcheng@redhat.com>
To: chuck.lever@oracle.com
Cc: nfs@lists.sourceforge.net
Subject: Re: [NFS] NFS Digest, Vol 18, Issue 70 (NFS performance problems)
Date: Sun, 25 Nov 2007 22:28:43 -0500	[thread overview]
Message-ID: <474A3D6B.2060208@redhat.com> (raw)
In-Reply-To: <47445727.5090705@oracle.com>

Chuck Lever wrote:

> Hi Wendy-
>
> That means his old system would have been exposed to data corruption 
> issues if it crashes (panic, power outage, etc).  Using "sync" became 
> default because async is inherently careless about data integrity.  
> The data loss is often entirely silent.
>
> This is explained in the Linux NFS FAQ, question B6.
>
> See http://nfs.sourceforge.net/index.php#faq_b6


Setting aside NFS for a moment...  for a locally mounted filesystem, the 
file data stays in the cache until write-back occurs. Upon crashing, 
there are always possibilities that the data could be lost. Journaling 
filesystems such as EXT3 can only ensure no meta-data corruption, there 
is no guarantee that data would be saved unless the filesystem is 
mounted with "sync" option. With non-trivial performance hits, most of 
the filesystems are hardly mounted with "sync" option. Applications 
normally understand the problem and whenever required, fsync() and/or 
similar mechanisms are applied.

For Linux NFS servers to deviate from this common practice, by reading 
the FAQ, I assume something has been done (particularly from client 
ends) to alleviate the performance hit ? Could you elaborate more about 
this ?

Again, I'm not trying to argue and/or start a flamewar. I have a need to 
understand more about this issue. The "sync" operation is very expensive 
for us (cluster filesystem) and I'm under the gun to improve our NFS 
file serving performance at this moment.

-- Wendy



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs


  reply	other threads:[~2007-11-26  3:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.194659.1195581701.26582.nfs@lists.sourceforge.net>
2007-11-20 20:22 ` [NFS] NFS Digest, Vol 18, Issue 70 (NFS performance problems) Wendy Cheng
     [not found]   ` <BAY104-W43766F661E50E7FFCDA8EBA7F0-MsuGFMq8XAE@public.gmane.org>
2007-11-20 21:17     ` Peter Staubach
2007-11-20 21:23       ` Wendy Cheng
2007-11-21 16:04         ` Chuck Lever
2007-11-26  3:28           ` Wendy Cheng [this message]
2007-11-26  4:41             ` Trond Myklebust
2007-11-26  5:02             ` J. Bruce Fields
     [not found]               ` <18254.19187.470275.538680@notabene.brown>
     [not found]                 ` <18254.19187.470275.538680-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-11-29  5:30                   ` Trond Myklebust
     [not found]                     ` <1196314230.7950.42.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2007-11-30 16:27                       ` Wendy Cheng
2007-12-03 20:31                         ` J. Bruce Fields
2007-12-03 21:13                           ` Wendy Cheng
2007-12-03 21:30                             ` J. Bruce Fields
2007-12-03 21:38                               ` J. Bruce Fields
2007-12-03 21:49                               ` Wendy Cheng
2007-12-03 22:07                                 ` J. Bruce Fields
2007-11-27 18:40           ` Rui Pedro Mendes Salgueiro
     [not found]             ` <20071127184050.GA13791-/uZbGGhPd8Gmv2Aub4FSgw@public.gmane.org>
2007-11-28  1:50               ` Chuck Lever

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=474A3D6B.2060208@redhat.com \
    --to=wcheng@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.