[Bug 306016] Re: nfs client broken since 2.6.28-2-generic upgrade

[mike503]

This has been an issue for me for a long time using intrepid too.

I have not upgraded to jaunty yet.

Kernel versions on only *one* machine seem to not start nlockmgr.

broken machine:

[root at lvs01 etc]# rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100024    1   udp  64054  status
    100024    1   tcp  49410  status
    100000    2   udp    111  portmapper

good machine:

[root at web02 default]# rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  26775  status
    100024    1   tcp  20961  status
    100021    1   tcp  17290  nlockmgr
    100021    3   tcp  17290  nlockmgr
    100021    4   tcp  17290  nlockmgr

same identical configs in /etc that matter, same everything. only one
machine out of 6 exhibited this behavior.

looks like adding "nolock" fixed this. but i was hoping the 2.6.28
update in intrepid would fix it and it still hasn't. the last stable
kernel i had was 2.6.24-16-server. since then every kernel has had this
issue just on this one box (all identically configured, identical dpkg
lists even - i dpkg -l and md5 them and i keep them identical...)

PLEASE have this fixed asap and if possible push it back to intrepid
until jaunty becomes the new production.

-- 
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.