From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jeff Layton <jlayton@redhat.com>
Cc: nfs@lists.sourceforge.net, nfsv4@linux-nfs.org
Subject: Re: [PATCH] NFS: have string-based mount options default to "intr" mounts
Date: Wed, 25 Jul 2007 16:16:57 -0400 [thread overview]
Message-ID: <1185394617.6585.135.camel@localhost> (raw)
In-Reply-To: <20070725154107.063c3b9a.jlayton@redhat.com>
On Wed, 2007-07-25 at 15:41 -0400, Jeff Layton wrote:
> On Wed, 25 Jul 2007 15:36:18 -0400
> Chuck Lever <chuck.lever@oracle.com> wrote:
>
> > I thought "nointr" was the default because it is safest.
> >
>
> I could see maybe with soft mounts, but in conjunction with a hard
> mount (which is the default) is there danger of corruption?
You may cause the sync to disk on close() to be aborted. The writes will
eventually get flushed to disk by the flushd() daemon, but failing to
sync writes to disk prior to closing the file is a violation of
close-to-open caching semantics and may cause corruption issues.
Trond
next prev parent reply other threads:[~2007-07-25 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 18:56 [PATCH] NFS: have string-based mount options default to "intr" mounts Jeff Layton
2007-07-25 19:36 ` Chuck Lever
2007-07-25 19:41 ` Jeff Layton
2007-07-25 19:48 ` Chuck Lever
2007-07-25 20:16 ` Trond Myklebust [this message]
2007-07-25 20:36 ` Peter Staubach
2007-07-26 2:44 ` Trond Myklebust
2007-07-25 20:43 ` Jeff Layton
2007-07-25 21:07 ` Peter Staubach
2007-07-25 23:48 ` Jeff Layton
2007-07-25 23:51 ` Jeff Layton
-- strict thread matches above, loose matches on Subject: below --
2007-07-25 20:05 [PATCH] NFS: have string-based mount options default to intr mounts Rick Macklem
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=1185394617.6585.135.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=jlayton@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
/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.