Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Josef Bacik <josef@redhat.com>,
	Andreas Dilger <adilger@dilger.ca>, "Ted Ts'o" <tytso@mit.edu>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] ext4: turn on i_version updates by default
Date: Tue, 15 May 2012 15:18:10 -0400	[thread overview]
Message-ID: <20120515191810.GA11028@fieldses.org> (raw)
In-Reply-To: <4FB2996F.40708@gmail.com>

On Tue, May 15, 2012 at 07:59:11PM +0200, Marco Stornelli wrote:
> Only a really really stupid question (I don't know NFS protocol well
> enough). In 3.3 kernel, I see that only ext4 uses MS_I_VERSION, so I
> wonder: if i_version change it's needed for exportable fs and so for
> nfs, other exportable fs?

Yes, it's needed for others as well.  I believe btrfs and xfs are both
adding it.

We're currently using ctime for the nfs change attribute.  That's
effectively jiffy granularity.  So to see the problem at a minimum you'd
need two writes to be processed within one jiffy, and a stat to come
between them.  But that's a correctness problem, and we'd like to see it
fixed before it becomes more common.

More generally, it's useful to be able to ask whether a file changed
without rereading all its data, and a clock that registers every change
and is consistent across a filesystem sounds difficult to scale.  We may
eventually find we need something like this outside nfs.

--b.

  reply	other threads:[~2012-05-15 19:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 14:06 [PATCH] ext4: turn on i_version updates by default J. Bruce Fields
2012-05-14 15:02 ` Andreas Dilger
2012-05-14 15:23   ` J. Bruce Fields
2012-05-14 17:27     ` Andreas Dilger
2012-05-14 17:58       ` Ted Ts'o
2012-05-14 18:33         ` Josef Bacik
2012-05-14 18:48           ` Jeff Layton
2012-05-14 18:51             ` Josef Bacik
2012-05-14 18:54           ` J. Bruce Fields
2012-05-14 19:05             ` Josef Bacik
2012-05-14 21:27               ` Andreas Dilger
2012-05-15 13:28                 ` Josef Bacik
2012-05-15 17:59                   ` Marco Stornelli
2012-05-15 19:18                     ` J. Bruce Fields [this message]
2012-05-15 17:33       ` J. Bruce Fields
2012-05-15 18:50         ` djwong
2012-05-14 23:08   ` Myklebust, Trond
2012-05-14 23:33     ` Andreas Dilger
2012-05-14 23:54       ` J. Bruce Fields
2012-05-15 10:30         ` Jan Kara
2012-05-15 12:35           ` J. Bruce Fields
2012-05-15 14:43             ` Jan Kara
2012-05-15  0:13       ` Myklebust, Trond

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=20120515191810.GA11028@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=adilger@dilger.ca \
    --cc=josef@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=marco.stornelli@gmail.com \
    --cc=tytso@mit.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox