nfs broken in net-next?

4 messages, 2 authors, 2009-10-29 · open the first message on its own page

nfs broken in net-next?

From: Yinghai Lu <hidden>
Date: 2009-10-28 20:13:53

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.


using opensuse11.1

YH

Re: nfs broken in net-next?

From: Suresh Jayaraman <hidden>
Date: 2009-10-29 07:02:45

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.
Is statd running on the server? The in-kernel statd has been replaced by
userspace statd.
using opensuse11.1

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

-- 
Suresh Jayaraman

Re: nfs broken in net-next?

From: Suresh Jayaraman <hidden>
Date: 2009-10-29 07:24:06

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)?

Thanks,

-- 
Suresh Jayaraman

Re: nfs broken in net-next?

From: Yinghai Lu <hidden>
Date: 2009-10-29 10:03:20

On Thu, Oct 29, 2009 at 12:23 AM, Suresh Jayaraman [off-list ref] wrote:
On 10/29/2009 01:43 AM, Yinghai Lu wrote:
quoted
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?
quoted
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.

YH
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help