From: "John Stoffel" <john@stoffel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
"J. Bruce Fields" <bfields@fieldses.org>,
Neil Brown <neilb@suse.de>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Failure to fallback to nfsd-v3 (?)
Date: Mon, 8 Feb 2010 12:25:20 -0500 [thread overview]
Message-ID: <19312.18688.846904.409496@stoffel.org> (raw)
In-Reply-To: <20100207083103.GA4602@infradead.org>
>>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:
Christoph> On Sun, Feb 07, 2010 at 05:23:49PM +0900, OGAWA Hirofumi wrote:
>> "J. Bruce Fields" <bfields@fieldses.org> writes:
>>
>> >> And the following commit seems to change the behavior.
>> >>
>> >> [nfsd4: fix error return when pseudoroot missing]
>> >> f39bde24b275ddc45df1ed835725b609e178c7a0
>> >>
>> >> Well, anyway, is this a expected behavior change, or something bug?
>> >
>> > It's expected. I'd recommend turning off nfsv4 on the server (add "-N4"
>> > to the rpc.nfsd commandline) for now.
>>
>> This looks like the silent user visible change. So, it would be better
>> to add more comment at least in changelog.
Christoph> Or rather it should be fixed. We should not silently break existing
Christoph> and probably rather common setups.
Hear hear! NFS should just gracefully fall back as far as it can. A
slow mount is better than NO mount. Esp when /home is mounted via
NFS.
John
next prev parent reply other threads:[~2010-02-08 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 3:32 Failure to fallback to nfsd-v3 (?) OGAWA Hirofumi
[not found] ` <87pr4h67rf.fsf-x/W9pkDDSe1TgC2z9Sl/nXf5DAMn2ifp@public.gmane.org>
2010-02-07 4:10 ` J. Bruce Fields
2010-02-07 8:23 ` OGAWA Hirofumi
[not found] ` <8763695u96.fsf-x/W9pkDDSe1TgC2z9Sl/nXf5DAMn2ifp@public.gmane.org>
2010-02-07 8:31 ` Christoph Hellwig
2010-02-08 17:25 ` John Stoffel [this message]
2010-02-08 18:31 ` J. Bruce Fields
2010-02-08 18:33 ` J. Bruce Fields
2010-02-09 16:55 ` J. Bruce Fields
2010-02-10 2:17 ` OGAWA Hirofumi
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=19312.18688.846904.409496@stoffel.org \
--to=john@stoffel.org \
--cc=bfields@fieldses.org \
--cc=hch@infradead.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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