User space automounter problems after upgrade to 2.6.25-rc9
----- Original Message ----
Quoted 49 lines
From: Benny Halevy <[email protected]>
To: Martin Knoblauch <[email protected]>
Cc: Trond Myklebust <[email protected]>; [email protected]; am-utils <[email protected]>
Sent: Tuesday, April 15, 2008 4:29:58 PM
Subject: Re: User space automounter problems after upgrade to 2.6.25-rc9Quoted 14 lines · Martin Knoblauch
----- Original Message ----
Quoted 13 lines
From: Trond Myklebust
To: Martin Knoblauch
Cc: [email protected]; am-utils
Sent: Tuesday, April 15, 2008 2:57:26 PM
Subject: Re: User space automounter problems after upgrade to 2.6.25-rc9Quoted 3 lines · Martin Knoblauch
Hi,
after booting a newly built 2.6.25-rc9 kernel, I see the following messages
and the user space automounter fails to work. Last good kernel for me is
2.6.24,
Quoted 19 lines
Quoted 19 lines
as -rc9 is my first attempt at 2.6.25. Extremely sorry for being late to the game :-(
Quoted 11 lines
[ 13.776876] Invalid hostname "pid4302@lpsdm60:/home" in NFS lock request [ 11.996757] Invalid hostname "pid4302@lpsdm60:/home" in NFS lock request [ 14.504927] Invalid hostname "pid4302@lpsdm60:/home" in NFS lock request [ 13.636860] Invalid hostname "pid4302@lpsdm60:/home" in NFS lock request [ 14.504927] Invalid hostname "pid4302@lpsdm60:/home" in NFS lock request [ 13.636860] Invalid hostname "pid4302@lpsdm60:/home" in NFS lock request [ 14.505079] Invalid hostname "pid4302@lpsdm60:/home" in NFS lock request [ 11.996757] Invalid hostname "pid4302@lpsdm60:/home" in NFS lock request [ 13.636860] Invalid hostname "pid4302@lpsdm60:/home" in NFS lock request [ 12.688801] Invalid hostname "pid4302@lpsdm60:/soft" in NFS lock requestQuoted 1 line
am-utils version is 6.1.5, config is attached
Already reported in:
http://bugzilla.kernel.org/show_bug.cgi?id=10349Quoted 6 lines
Quoted 4 lines
The problem is due to known bugs in the am-utils mount code (no, 'pid4302@lpsdm60:/soft' is not and has never been a valid server hostname).
I always wondered, but never asked :-) Apparently the kernel did never care
until recently.
Quoted 1 line
Quoted 9 lines
Quoted 5 lines
Quoted 3 lines
The workaround should be to turn off locking by adding the 'nolock' mount flag.
Not sure what kind of side effects that will have. Probably better to stay at
2.6.24 and wait for a fix in am-utils.
FWIW, autofs works for me (Fedora 7, 2.6.25-rc*).
good to know, but not really an option here. The customer in question has several hundred workstations and servers using am-utils and the map-management is completely out of my hands.
Cheers
Martin