NFS lock problem

Aubrey aubreylee at gmail.com
Mon Mar 20 09:27:17 UTC 2006


Hi all,

I'm working on the blackfin uclinux platform. When I mounted the nfs
as the root file system, the syscall "fcntl" can lock file
successfully. But when I start up kernel and mount(busybox) the nfs on
a local directory, the syscall "fcntl" can't lock the file. The error
log as follows:
===================
<5>Jan  6 06:06:29 kernel: lockd: cannot monitor 192.168.0.2
<5>Jan  6 06:06:29 kernel: lockd: failed to monitor 192.168.0.2
<7>Jan  6 06:06:30 kernel: nsm_mon_unmon: rpc failed, status=-13
===================
It seems the lockd wasn't started. But the mount parameter was:
===================
192.168.0.2:/romfs on /mnt type nfs
(rw,v3,rsize=32768,wsize=32768,hard,udp,lock,addr=192.168.0.2)
===================
I didn't use the "nolock" option, So I thought the lockd should be
started by busybox-mount command.
Is it a bug of busybox or I'm wrong?
Thanks for your hints!

Regards,
-Aubrey



More information about the busybox-cvs mailing list