From: tytso@mit.edu
To: Ben Hutchings <ben@decadent.org.uk>
Cc: 738758@bugs.debian.org, Christoph Hellwig <hch@infradead.org>,
Andreas Dilger <adilger@dilger.ca>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
"1o5g4r8o@gmail.com" <1o5g4r8o@gmail.com>
Subject: Re: Bug#738758: [PATCH] ext4: kill i_version support for Hurd-castrated file systems
Date: Fri, 21 Mar 2014 10:39:27 -0400 [thread overview]
Message-ID: <20140321143927.GA31179@thunk.org> (raw)
In-Reply-To: <1395336632.2770.13.camel@deadeye.wl.decadent.org.uk>
On Thu, Mar 20, 2014 at 05:30:32PM +0000, Ben Hutchings wrote:
>
> It looks like ext2 and ext3 would always initialise i_version to 1 in
> memory; does it matter that you're changing that to 0 for Hurd
> filesystems?
No, NFS only cares that the i_version number has changed, and it's
mainly important if you have two clients trying to simultaneously
access the same file, so they get a signal that they need to
invalidate their locally cached metadata (or data, in the case of
NFSv4). But Hurd only supports NFSv2, and the performance is such
that I doubt anyone would be all that interested in using a Hurd
server as a NFS server for even a small workgroup, let alone a
department, so this is unlikely to be a big deal.
Cheers,
- Ted
next prev parent reply other threads:[~2014-03-21 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140212185534.GA4005@phenomenon>
2014-03-19 20:20 ` Bug#738758: linux-image-3.12-1-amd64: ext4 can't properly handle ext2 filesystems created for GNU/Hurd Gabriele Giacone
2014-03-20 4:34 ` [PATCH] ext4: kill i_version support for Hurd-castrated file systems Theodore Ts'o
2014-03-20 5:27 ` Andreas Dilger
2014-03-20 8:10 ` Christoph Hellwig
2014-03-20 14:44 ` tytso
2014-03-20 17:30 ` Bug#738758: " Ben Hutchings
2014-03-21 14:39 ` tytso [this message]
2014-03-21 16:48 ` [PATCH] ext4: optimize Hurd tests when reading/writing inodes Theodore Ts'o
2014-03-21 17:11 ` Bug#738758: " Samuel Thibault
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=20140321143927.GA31179@thunk.org \
--to=tytso@mit.edu \
--cc=1o5g4r8o@gmail.com \
--cc=738758@bugs.debian.org \
--cc=adilger@dilger.ca \
--cc=ben@decadent.org.uk \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).