Re: User space automounter problems after upgrade to 2.6.25-rc9

[Trond Myklebust]

On Tue, 2008-04-15 at 04:28 -0700, Martin Knoblauch wrote:
> 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

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/