From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chris Fanning <christopher.fanning@gmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [NFS] async vs. sync. corrupted fs
Date: Mon, 19 May 2008 10:54:11 -0400 [thread overview]
Message-ID: <20080519145411.GC7622@fieldses.org> (raw)
In-Reply-To: <215ff4410805160355x25b8d055x9a0a246aa5875482-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, May 16, 2008 at 12:55:59PM +0200, Chris Fanning wrote:
> Hello all,
>
> Could someone help me out?
>
> I'm exporting a whole partition to a client.
> Using (rw,no_root_squash,sync, no_subtree_check), when I shutdown the
> server _before_ the client, the filesystem on the partion becomes
> corrupted.
How do you know it becomes corrupted?
> When I user async, it doesn't happen.
"async" the client-side mount option, or "async" the server-side export
option?
> Is this normal?
No.
> The exports manpage suggests that 'sync' is the better option.
Yes.
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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
next prev parent reply other threads:[~2008-05-19 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 10:55 [NFS] async vs. sync. corrupted fs Chris Fanning
[not found] ` <215ff4410805160355x25b8d055x9a0a246aa5875482-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-19 14:54 ` J. Bruce Fields [this message]
2008-05-20 8:00 ` Chris Fanning
[not found] ` <215ff4410805200100o20fb83bcm9921127efef27ef9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-20 13:01 ` Trond Myklebust
2008-05-20 14:05 ` Marcelo Leal
[not found] ` <42996ba90805200705o49b4a17bn62cc9962bbcac8b2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-20 16:27 ` Trond Myklebust
2008-05-20 18:56 ` Marcelo Leal
[not found] ` <215ff4410805200100o20fb83bcm9921127efef27ef9-JsoAwUIsXouhRSP0FMvGiw@public.gmane.org m>
2008-05-20 13:36 ` Talpey, Thomas
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=20080519145411.GC7622@fieldses.org \
--to=bfields@fieldses.org \
--cc=christopher.fanning@gmail.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.