From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Neil Brown <neilb@suse.de>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Failure to fallback to nfsd-v3 (?)
Date: Wed, 10 Feb 2010 11:17:17 +0900 [thread overview]
Message-ID: <877hqln8b6.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20100209165547.GB29091@fieldses.org> (J. Bruce Fields's message of "Tue, 9 Feb 2010 11:55:47 -0500")
"J. Bruce Fields" <bfields@fieldses.org> writes:
>> > > 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.
>> >
>> > Well, anyway, thanks. (BTW, I assumed rpc.nfsd is typo of rpc.mountd)
>>
>> No, the -N4 tells rpc.mountd to turn off NFSv4 support before starting
>
> (Hah!--trying to correct you, I got it wrong myself--I really did mean
> rpc.*nfsd*, not rpc.mountd.)
Oh, I was reading very old man page. Thanks for correcting.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2010-02-10 2:17 UTC|newest]
Thread overview: 12+ 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 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-07 8:31 ` Christoph Hellwig
2010-02-08 17:25 ` John Stoffel
2010-02-08 18:31 ` J. Bruce Fields
2010-02-08 18:33 ` 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 [this message]
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=877hqln8b6.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=bfields@fieldses.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.