From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Neil Brown <neilb@suse.de>,
linux-nfs@vger.kernel.org, Theodore Tso <tytso@mit.edu>
Subject: Re: Thoughts about cache consistency and directories in particular.
Date: Thu, 23 Apr 2009 18:24:41 -0400 [thread overview]
Message-ID: <1240525481.8583.23.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20090423220742.GD1906@fieldses.org>
On Thu, 2009-04-23 at 18:07 -0400, J. Bruce Fields wrote:
> On Thu, Apr 23, 2009 at 05:52:57PM -0400, Trond Myklebust wrote:
> > On Thu, 2009-04-23 at 17:34 -0400, J. Bruce Fields wrote:
> > > On Tue, Apr 21, 2009 at 05:43:49PM -0400, bfields wrote:
> > > > Actually, I did this and then realized: I'm using IS_I_VERSION(inode) to
> > > > turn on use of the i_version as the change attribute on both files and
> > > > directories. But it actually only makes a difference for files.
> > > >
> > > > So I guess I should just be using i_version as the change attribute
> > > > unconditionally for directories? (Will that work on any filesystem?)
> > >
> > > I'm still curious about this.
> >
> > Few of the common filesystems actually store dir->i_version on permanent
> > storage,
>
> Hopefully ext4 is, at least in the IS_I_VERSION(inode) case?
It looks to me as though ext4 always saves inode->i_version provided you
are using the default 256 byte inode size. Ted?
Trond
next prev parent reply other threads:[~2009-04-23 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 2:18 Thoughts about cache consistency and directories in particular Neil Brown
2009-02-20 18:23 ` J. Bruce Fields
2009-02-20 19:47 ` Neil Brown
[not found] ` <18847.2286.101191.989726-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-02-20 20:14 ` J. Bruce Fields
2009-02-20 21:04 ` Neil Brown
[not found] ` <18847.6886.50844.260910-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-04-21 21:43 ` J. Bruce Fields
2009-04-23 21:34 ` J. Bruce Fields
2009-04-23 21:52 ` Trond Myklebust
[not found] ` <1240523577.8583.13.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-23 22:07 ` J. Bruce Fields
2009-04-23 22:24 ` Trond Myklebust [this message]
[not found] ` <18846.4842.625445.980681-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-02-20 18:56 ` Trond Myklebust
2009-02-20 19:52 ` Neil Brown
[not found] ` <18847.2578.480148.216735-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-02-20 20:32 ` Trond Myklebust
2009-02-20 21:06 ` Neil Brown
[not found] ` <18847.6988.418374.839185-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-02-20 22:14 ` Trond Myklebust
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=1240525481.8583.23.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--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