Public bug reported:
I've tried AMD64 2.6.28-2.3-generic with Jaunty userspace, and with
Intrepid userspace, and NFS is b0rked with both (nfs client and nfs
server). Mounts work with -o nolock, though. (-o nolock doesn't
require NFS lockd to be running). Otherwise, NFS mount attempts time
out.
nfs-common's /etc/init.d script fails, and it runs that in postinst, so
this should be reproducible for anyone, even if they don't normally use
NFS. And nfs-kernel-server won't start either, even with an empty
/etc/exports. (I tried running /etc/init.d/nfs-kernel-server.dpkg-new
in my Jaunty chroot, where the nfs pkgs are blocked by nfs-common's
postinst.) Just install nfs-common, and if it fails to configure
(because invoke-rc.d failed), then this is the bug I'm talking about.
This was a problem with the first Jaunty 2.6.28-1-ub-generic kernel,
too. Intrepid's 2.6.27-10 is ok.
As I said, I was able to reproduce this by booting to my Jaunty chroot,
where I didn't previously have nfs-common installed at all, so it's not
a stale config file causing problems.
I searched around some, expecting other people would have hit this, but
maybe not many people use NFS on the systems where they play around with
new kernels. Otherwise, maybe I just missed finding an already reported
bug, or worse, this isn't as reproducible as I'm hoping.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
nfs lockd broken
https://bugs.launchpad.net/bugs/306343
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
