[Pkg-sysvinit-devel] Bug#578254: nfs mounts are not working at boot

[Michael Tokarev]

Package: initscripts
Version: 2.87dsf-10
Severity: normal

It appears that NFS mounts are not working at bootup anymore.
Not sure since what time.

Here's a typical boot log with ASYNCMOUNTNFS is not set:

 Setting up networking....
 Configuring network interfaces...if-up.d/mountnfs[br0]: waiting for interface tap-kvm before doing NFS mounts (warning).
 if-up.d/mountnfs[br0]: waiting for interface tap-kvm0 before doing NFS mounts (warning).
 if-up.d/mountnfs[br0]: waiting for interface tap-kvm1 before doing NFS mounts (warning).
 if-up.d/mountnfs[br0]: waiting for interface eth0 before doing NFS mounts (warning).
 if-up.d/mountnfs[tap-kvm]: waiting for interface tap-kvm0 before doing NFS mounts (warning).
 if-up.d/mountnfs[tap-kvm]: waiting for interface tap-kvm1 before doing NFS mounts (warning).
 if-up.d/mountnfs[tap-kvm]: waiting for interface eth0 before doing NFS mounts (warning).
 if-up.d/mountnfs[tap-kvm0]: waiting for interface tap-kvm1 before doing NFS mounts (warning).
 if-up.d/mountnfs[tap-kvm0]: waiting for interface eth0 before doing NFS mounts (warning).
 if-up.d/mountnfs[tap-kvm1]: waiting for interface eth0 before doing NFS mounts (warning).
 Starting portmap daemon....
 Starting NFS common utilities: statd idmapd.
 mount.nfs4: No route to host
 done.

Note the pre-last line: I think it's the problematic one.

And here's the fstab entry:

 gnome:/  /net/gnome  nfs4  bg,nodev,nosuid     0 0

When ASYNCMOUNTNFS is set to no in rcS, the same happens:

 Setting up networking....
 Configuring network interfaces...done.
 Starting portmap daemon....
 Starting NFS common utilities: statd idmapd.
 Starting portmap daemon...Already running..
 Starting NFS common utilities: statd idmapd.
 mount.nfs4: No route to host
 Cleaning up temporary files....

except that the boot process is now much more clean,
without the annoying warnings.

I can only guess that when the mount is performed,
the interface is not initialized yet, and is not
ready to use.  But on the other hand, it looks like
the network is up'n'running at this time, since
the 'Configuring network interfaces' stage has been
completed.

The /etc/network/interfaces here has nothing
fancy.  The main interface is a bridge, which should
be up-n-running immediately, even if physical ifaces
are not yet ready:

auto br0
iface br0 inet static
 address 192.168.88.2
 netmask 255.255.255.0
 gateway 192.168.88.4
 bridge-ports all
 bridge-maxwait 0


-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (990, 'stable'), (60, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.33-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages initscripts depends on:
ii  coreutils                    7.4-2       The GNU core utilities
ii  debianutils                  2.30        Miscellaneous utilities specific t
ii  libc6                        2.10.2-6    Embedded GNU C Library: Shared lib
ii  lsb-base                     3.2-20      Linux Standard Base 3.2 init scrip
ii  mount                        2.16.2-0    Tools for mounting and manipulatin
ii  sysv-rc                      2.86.ds1-61 System-V-like runlevel change mech
ii  sysvinit-utils               2.87dsf-10  System-V-like utilities

Versions of packages initscripts recommends:
ii  e2fsprogs                     1.41.10-1  ext2/ext3/ext4 file system utiliti
ii  psmisc                        22.6-1     Utilities that use the proc filesy

initscripts suggests no packages.

-- no debconf information