[Virtual-pkg-base-maintainers] Bug#754342: nfsroots: "mount: Device or ressource busy"

[Gilles MOREL]

  I build my diskless client with the Ubuntu 14.04's debootstrap version. I made a basic bootable version and I added the desktop environment from that.

  For the export, I used this line. I used the same config for Ubuntu 13.04, 13.10 and 14.04 and I did not change this for debian :
/mnt/rootfs/stardust            192.168.20.50(rw,async,no_subtree_check,no_root_squash)

  I'm not a nfs expert, but I think it's a nfsv3 configuration.
  I don't have any wheezy client, but I think the problem comes from the initramfs that tries to mount the rootfs a second time.
  For info, this is my boot command line for this host :
kernel tftp://192.168.20.1//systems/stardust/vmlinuz ip=dhcp nfsroot=192.168.20.1:/mnt/rootfs/stardust root=/dev/nfs rw rootdelay=10 initrd tftp://192.168.20.1//systems/stardust/initrd.img

  I don't have a line in the client's fstab for the rootfs.
--
Gilles Émilien MOREL <contact at gilles-morel.fr>
Le premier tirage aléatoire est [31, 19, 69, 10, 28] et le second est [9, 9, 9, 9, 9]. Quel tirage est le plus aléatoire ?


----- Message original ----------------
Holger Levsen <holger at layer-acht.org>
à Gilles MOREL <contact at gilles-morel.fr>, 754342 at bugs.debian.org
copie à 
le jeudi 10 juillet 2014 à 11:05:17
avec KMail/1.13.7 (Linux/3.14-0.bpo.1-amd64; KDE/4.8.4; x86_64; ; )

Re: Bug#754342: nfsroots: "mount: Device or ressource busy"
--------------------------------------------------
control: tags -1 + moreinfo

Hi Gilles,

On Donnerstag, 10. Juli 2014, Gilles MOREL wrote:
>   When I boot my diskless client, I got a message on console:

how did you build your diskless client?

>   I got messages in the server (debian) syslog:
> Jul  9 08:36:03 Magnet rpc.mountd[31825]: authenticated mount request from
> 192.168.20.50:962 for /mnt/rootfs/stardust (/mnt/rootfs/stardust)         

how does your /etc/export look on the server, are you using nfs2/3/4?

Did you have wheezy clients with the same server which dont show this 
behaviour?


cheers,
	Holger