Skip to contentSkip to conversation

User space automounter problems after upgrade to 2.6.25-rc9

DISCUSSION Martin Knoblauch 3 participants 3 messages Apr 15, 2008

lore
Share & tools
lore
#0 lore raw

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 :-(

[   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 request

am-utils version is 6.1.5, config is attached

Cheers
Martin
------------------------------------------------------
Martin Knoblauch

email: k n o b i AT knobisoft DOT de
www:   http://www.knobisoft.de
#1 lore raw
Quoted 15 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 :-(

[   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 request
Quoted 9 lines

am-utils version is 6.1.5, config is attached

Cheers
Martin
------------------------------------------------------
Martin Knoblauch

email: k n o b i AT knobisoft DOT de
www:   http://www.knobisoft.de

Martin, thanks for the report.
This is a known problem.
See http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/2f45e12c9e4e41a2/344607c434ea1040

Benny

#2 lore raw
In reply to Martin Knoblauch
Quoted 15 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 :-(

[   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 request
Quoted 1 line

am-utils version is 6.1.5, config is attached

Already reported in:
http://bugzilla.kernel.org/show_bug.cgi?id=10349
and
https://bugzilla.am-utils.org/show_bug.cgi?id=612

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).

The workaround should be to turn off locking by adding the 'nolock' mount flag.

Trond