User space automounter problems after upgrade to 2.6.25-rc9
----- Original Message ----
Quoted 28 lines
From: Trond Myklebust <[email protected]>
To: Martin Knoblauch <[email protected]>
Cc: [email protected]; am-utils <[email protected]>
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, as -rc9 is my first attempt at 2.6.25. Extremely sorry for being late to the game :-(
Quoted 12 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
Quoted 9 lines
Already reported in:
http://bugzilla.kernel.org/show_bug.cgi?id=10349and
https://bugzilla.am-utils.org/show_bug.cgi?id=612The 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 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.
Cheers
Martin
Quoted 37 lines · Martin Knoblauch
----- Original Message ----
Quoted 26 lines
From: Trond Myklebust <[email protected]>
To: Martin Knoblauch <[email protected]>
Cc: [email protected]; am-utils <[email protected]>
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, 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
Quoted 9 lines
Already reported in:
http://bugzilla.kernel.org/show_bug.cgi?id=10349and
https://bugzilla.am-utils.org/show_bug.cgi?id=612The 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).
Quoted 7 lines
I always wondered, but never asked :-) Apparently the kernel did never care until recently.
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*).
Benny
Quoted 5 lines
Cheers
Martin
Quoted 1 line · Martin Knoblauch
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.
2.6.24 has exactly the same problem. It is just that the kernel will report it much later (essentially the first time that you try to lock a file).
Trond