From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756374AbYDOPsS (ORCPT ); Tue, 15 Apr 2008 11:48:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751849AbYDOPsF (ORCPT ); Tue, 15 Apr 2008 11:48:05 -0400 Received: from web32608.mail.mud.yahoo.com ([68.142.207.235]:33021 "HELO web32608.mail.mud.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752080AbYDOPsE (ORCPT ); Tue, 15 Apr 2008 11:48:04 -0400 X-YMail-OSG: AcFnn48VM1lG9CzldFSonbC2qpQ1gAAqzWu06yMguuW3sTkp2eLvSsqf7Y2K1nz8MT9Mpw-- X-Mailer: YahooMailRC/902.40 YahooMailWebService/0.7.185 Date: Tue, 15 Apr 2008 08:47:59 -0700 (PDT) From: Martin Knoblauch Subject: Re: User space automounter problems after upgrade to 2.6.25-rc9 To: Benny Halevy Cc: Trond Myklebust , linux-kernel@vger.kernel.org, am-utils MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <469619.11800.qm@web32608.mail.mud.yahoo.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ----- Original Message ---- > From: Benny Halevy > To: Martin Knoblauch > Cc: Trond Myklebust ; linux-kernel@vger.kernel.org; am-utils > Sent: Tuesday, April 15, 2008 4:29:58 PM > Subject: Re: User space automounter problems after upgrade to 2.6.25-rc9 > > On Apr. 15, 2008, 16:58 +0300, Martin Knoblauch wrote: > > ----- Original Message ---- > >> From: Trond Myklebust > >> To: Martin Knoblauch > >> Cc: linux-kernel@vger.kernel.org; am-utils > >> Sent: Tuesday, April 15, 2008 2:57:26 PM > >> Subject: Re: User space automounter problems after upgrade to 2.6.25-rc9 > >> > >> > >> 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). > >> > > > > I always wondered, but never asked :-) Apparently the kernel did never care > until recently. > > > >> 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