nfsroot nolock regression

[Aron Griffis]

Binary package hint: mountall

I just updated a headless thin client from jaunty to karmic. Now it fails to boot with this:

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.
mountall: mount / [564] terminated with status 32
mountall: Filesystem could not be mounted: /

The relevant kernel parameters are:

ip=::::nord::dhcp root=/dev/nfs nfsroot=16.1.1.1:/export/olio,nolock

and /etc/fstab is empty. I've also tried putting configuration in /etc/fstab then regenerating the initramfs, but that doesn't seem to matter so I reverted to the configuration that worked in jaunty.

It seems like mountall is dropping the "nolock" option from the nfsroot kernel param?

[Aron Griffis (agriffis)]

Btw I'm running mountall-0.2.2

[Aron Griffis (agriffis)]

Okay, by adding this to my /etc/fstab on the nfs root filesystem, then regenerating the initramfs, it's booting again:

/dev/nfs / nfs nolock,tcp 0 0

So this differs from my jaunty config in two ways:

1. jaunty didn't require nolock. I don't know if it was being automagically added by mountall or what, but an nfsroot system would boot just fine without specifying nolock anywhere.

2. since karmic seems to ignore nolock in the kernel nfsroot parameter, my karmic config now requires an /etc/fstab whereas jaunty did not.

[Scott James Remnant (Canonical) (canonical-scott)]

Reassigned to initramfs-tools, since that is (I think) what parses that option - it must not be ending up in mountinfo correctly