From: Yinghai Lu <yhlu.kernel@gmail.com>
To: Suresh Jayaraman <sjayaraman@suse.de>,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetDev <netdev@vger.kernel.org>
Subject: Re: nfs broken in net-next? -- now in mainline
Date: Wed, 9 Dec 2009 12:34:36 -0800 [thread overview]
Message-ID: <86802c440912091234t74fd2311t33c85379c06dd55c@mail.gmail.com> (raw)
On Thu, Oct 29, 2009 at 2:03 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> On Thu, Oct 29, 2009 at 12:23 AM, Suresh Jayaraman <sjayaraman@suse.de> wrote:
>> On 10/29/2009 01:43 AM, Yinghai Lu wrote:
>>> pk12-3214-189-102:~ # mount -t nfs 10.6.75.100:/data/shared/pxeboot /x
>>> mount.nfs: rpc.statd is not running but is required for remote locking.
>>> mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
>>
>> rpc.statd on client should have be started by mount.nfs when a nfs
>> filesystem is mounted. Is this not happening for some reason or do you
>> see any errors in syslog?
>>
>>>
>>> using opensuse11.1
>>>
>>
>> Are you using 11.1 betas? I know of a problem where non-root user mounts
>> fail to start rpc.statd in betas that got fixed later:
>>
>> http://marc.info/?l=linux-nfs&m=122748525624094&w=2
>>
>> Is the problem seen only recently (after updating to net-next)?
>>
>
> only happen with net-next.
>
> linus tree and tip tree are ok.
>
Finally it reached linus tree and tip.
YH
next reply other threads:[~2009-12-09 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 20:34 Yinghai Lu [this message]
2009-12-10 7:33 ` Ingo Molnar
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=86802c440912091234t74fd2311t33c85379c06dd55c@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=sjayaraman@suse.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®