[Bug 452686] Re: nfsroot nolock regression

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The Ubuntu version this bug was reported against reached
end-of-life. We appreciate that this bug may be old and you might not be
interested in discussing it anymore. But if you are then please upgrade
to the latest Ubuntu version and re-test. If you then find the bug is
still present in the newer Ubuntu version, please add a comment here
telling us which new version it is in.

** Changed in: initramfs-tools (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/452686

Title:
  nfsroot nolock regression

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/452686/+subscriptions