Package: mount Version: 2.13.1.1-1 Severity: important
mounting filesystems at boot time calls /etc/network/if-up.d/mountnfs when it comes time to mount nfs mounted filesystems. The script depends on a lock, /var/run/network/mountnfs, which if it exists the script bails out on the basis of trying to avoid a race or double invocation. Unfortunately, this lock can fail to be removed and so a reboot of the machine in question will fail to remove the lock and mountnfs will abort all mounts because the lock is still in place. You can reproduce this problem easy enough: give yourself an nfs mount in /etc/fstab such as: x.x.x.x:/nfsmount /nfs nfs defaults 0 0 and verify your filesystem is mounted (eg: mount -a) then mkdir -p /var/run/network/mountnfs and reboot your machine. That file system will not be mounted again until you manually remove /var/run/network/mountnfs The lock can get left in place due to a variety of reasons such as server crash or the like. The fix should be that, somewhere, at least this part of /var/run should get wiped out on reboot before anything else happens. -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31mike (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mount depends on: ii libblkid1 1.41.3-1 block device id library ii libc6 2.7-18 GNU C Library: Shared libraries ii libselinux1 2.0.65-5 SELinux shared libraries ii libuuid1 1.41.3-1 universally unique id library mount recommends no packages. Versions of packages mount suggests: ii nfs-common 1:1.1.2-6lenny1 NFS support files common to client -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
