Bug#580155: mount: Unclear message - mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
Package: mount
Version: 2.16.2-0
Severity: minor
A typical situation:
$ umount -fl /home ; mount /home
umount: /home: not mounted
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.
mount.nfs: an incorrect mount option was specified
Hm?
$ ls /etc/init.d/*stat*
<noting>
Eh?
$ /etc/init.d/nfs-kernel-server stop ; /etc/init.d/nfs-kernel-server start
That should do it, let's check:
$ umount -fl /home ; mount /home
umount: /home: not mounted
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.
mount.nfs: an incorrect mount option was specified
No kidding? ..it appears that the magic happens in:
$ /etc/init.d/nfs-common stop ; /etc/init.d/nfs-common start
$ umount -fl /home ; mount /home
BINGO!
SUGGESTION
If possible, please improve the error message to point to restart
/etc/init.d/nfs-common
under Debian, because the message "start statd" isn't very helpful.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mount depends on:
ii libblkid1 2.16.2-0 block device id library
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libselinux1 2.0.94-1 SELinux runtime shared libraries
ii libsepol1 2.0.40-2 SELinux library for manipulating b
ii libuuid1 2.16.2-0 Universally Unique ID library
mount recommends no packages.
Versions of packages mount suggests:
ii nfs-common 1:1.2.2-1 NFS support files common to client
-- no debconf information
Reply to: