From: "Theodore Ts'o" <tytso@mit.edu>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
William Koh <kkc6196@fb.com>, Andreas Dilger <adilger@dilger.ca>,
linux-ext4 <linux-ext4@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] fs: ext4: inode->i_generation not assigned 0.
Date: Wed, 5 Jul 2017 16:27:50 -0400 [thread overview]
Message-ID: <20170705202750.j5texbm2xdxnph6m@thunk.org> (raw)
In-Reply-To: <20170705191933.GA6297@magnolia>
On Wed, Jul 05, 2017 at 12:19:33PM -0700, Darrick J. Wong wrote:
>
> So, what's the probability that there are clients out there that started
> talking to a 2.2-based knfsd and will now want to talk to a modern 4.13
> kernel seventeen years later? (Do nfs handles persist across client
> restarts/remounts?)
It's whether or not nfs handles persist across server restarts which
would be the more interesting question. So if you had a NAS box that
was using a Linux 2.2 kernel, and you had clients access the box, and
then that box gets upgraded to use a 4.13 kernel, what happens?
In the ideal world, the client wouldn't notice, and its 2.2-based file
handles that it obtained while the 2.2 kernel was running would
continue to work after the box came back up running the new 4.13
kernel.
To be honest, I'm not sure I care that much, but I don't use NFS much
if at all these days myself. And in reality, what's the chance that
an NAS box vendor would continue to support a box that is 17 years old
and provide an upgrade for it? (OK, everyone can stop laughing now. :-)
- Ted
next prev parent reply other threads:[~2017-07-05 20:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 22:06 [PATCH] fs: ext4: inode->i_generation not assigned 0 Kyungchan Koh
2017-06-29 0:48 ` Darrick J. Wong
2017-06-29 0:58 ` William Koh
2017-06-29 2:32 ` Andreas Dilger
2017-06-29 4:37 ` William Koh
2017-06-29 4:59 ` Darrick J. Wong
2017-06-29 14:28 ` William Koh
2017-06-29 14:35 ` J. Bruce Fields
2017-06-29 17:25 ` Darrick J. Wong
2017-06-29 18:30 ` J. Bruce Fields
2017-06-29 18:50 ` J. Bruce Fields
2017-07-04 4:04 ` Darrick J. Wong
2017-07-05 1:15 ` J. Bruce Fields
2017-07-05 19:19 ` Darrick J. Wong
2017-07-05 20:27 ` Theodore Ts'o [this message]
2017-07-07 10:51 ` Jeff Layton
2017-07-07 15:51 ` Theodore Ts'o
2017-07-07 16:13 ` Jeff Layton
2017-07-07 16:47 ` J. Bruce Fields
2017-07-05 20:49 ` J. Bruce Fields
2017-07-06 1:08 ` NeilBrown
2017-07-06 2:39 ` J. Bruce Fields
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=20170705202750.j5texbm2xdxnph6m@thunk.org \
--to=tytso@mit.edu \
--cc=Kernel-team@fb.com \
--cc=adilger@dilger.ca \
--cc=bfields@fieldses.org \
--cc=darrick.wong@oracle.com \
--cc=kkc6196@fb.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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).