Thread: NFS 3 with Karmic 9.10 client does not mount - rpc.statd issue
i had weird experience related mounting gutsy nfs share @ boot time on karmic client.
described in post:
http://ubuntuforums.org/showthread.p...76#post8603076
work around (aka add nolock in /etc/fstab mount stanza). however, happens without nolock,
must trust rpc.statd it's job.
clearly, error message in karmic start proves not working expected:
comparing processes ps aux on how started on debian (on pc):mountall: event failed
mount.nfs: rpc.statd not running required remote locking.
either use '-o nolock' keep locks local, or start statd.
mountall: mount /home/jamb/nfs [819] terminated status 32
mountall: filesystem not mounted: /home/jamb/nfs
with karmic ps aux:debian lenny 32-bit:
owner command
daemon /sbin/portmap
statd /sbin/rpc.statd
why comparison, karmic use 2.6.31-16 kernel, use l-option, rewritten portmap , use mountall binary.karmic 9.10 32-bit:
owner command
daemon portmap
statd rpc.statd -l
original fstab mount stanza works expected on jaunty (9.04), intrepid (8.10), hardy (9.04), gutsy (7.10) , debian lenny (5.03).
l option in rpc.statd means (from man):
-l, --no-notify
inhibits running of sm-notify.
if sm-notify run some other script @ boot time,
there no need statd start sm-notify itself.
can appropriate if starting of statd needs delayed until need.
in such cases sm-notify should still run @ boot time.
there 1 bug report related sm-notify here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502122
launchpad have bug report related mountall , nfs:
https://bugs.launchpad.net/ubuntu/+s...ll/+bug/485709
, nfs4
http://https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/501678
let me if have had similar experiences this, , i'm curious why see in karmic not on previous releases?
file mountall bug after having sit here few more days.
Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Installation & Upgrades [all variants] NFS 3 with Karmic 9.10 client does not mount - rpc.statd issue
Ubuntu
Comments
Post a Comment