From: Kinglong Mee <kinglongmee@gmail.com>
To: Houlinfei <hou.linfei@h3c.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Cc: "bfields@fieldses.org" <bfields@fieldses.org>,
"neilb@suse.com" <neilb@suse.com>,
"SteveD@redhat.com" <SteveD@redhat.com>,
Kinglong Mee <kinglongmee@gmail.com>
Subject: Re: some problems about nfs mount
Date: Tue, 14 Mar 2017 16:28:24 +0800 [thread overview]
Message-ID: <d15aa1b9-b0f6-d9d3-4853-d83f57dcfabb@gmail.com> (raw)
In-Reply-To: <d8a1fbe6-0373-ea97-16d3-c9c4b5e49880@gmail.com>
On 3/14/2017 13:41, Kinglong Mee wrote:
> On 3/14/2017 11:52, Houlinfei wrote:
>> hi Kinglong:
>> There has no firewall. While my client system is Ubuntu 14.04, it's ok.
>> There has problem on ubuntu12.04 system. But if I add a parameter sec=sys, it is also ok. Such as, #mount -t nfs -o sec=sys 193.168.70.26:/root/hh /mnt/uu
>> But when my mount command line t is #mount -t nfs 193.168.70.26:/root/hh /mnt/uu it fail.
>> There is some client fail log:
>
> The ubuntu12.04 system contains an old kernel, the problem should be a bug in that kernel.
> I don't have an old kernel as ubuntu12.04 system, so I don't check the code.
>
> Can you have a try with the following patch ?
> Your can get more information from the comments in the patch.
>
> Commit 4580a92d4 ("NFS: Use server-recommended security flavor by default"),
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4580a92d4
>
Sorry, please ignore the above comments.
I don't think it's useful, I will find an ubuntu12.04 and have a check.
thanks,
Kinglong Mee
next prev parent reply other threads:[~2017-03-14 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 3:52 some problems about nfs mount Houlinfei
2017-03-14 5:41 ` Kinglong Mee
2017-03-14 8:28 ` Kinglong Mee [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-14 8:47 Houlinfei
2017-03-14 14:45 ` Kinglong Mee
2017-03-13 3:42 houlinfei
2017-03-13 4:02 ` Kinglong Mee
2017-03-10 16:24 houlinfei
2017-03-11 0:10 ` Kinglong Mee
2017-03-11 0:12 ` Kinglong Mee
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=d15aa1b9-b0f6-d9d3-4853-d83f57dcfabb@gmail.com \
--to=kinglongmee@gmail.com \
--cc=SteveD@redhat.com \
--cc=bfields@fieldses.org \
--cc=hou.linfei@h3c.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.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).