AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071010081540.2b5a7773@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<acooke@css.glasshouse.com>,<dl-cstech@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	200710101416.l9AEGJl02081@mailhost-rtp.css.glasshouse.com
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 10 Oct 2007 08:16:49 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: <acooke@css.glasshouse.com>
Cc: "'dl-cstech'" <dl-cstech@onstor.com>
Subject: Re: RPC program not registered error messages - case 6092
Message-ID: <20071010081649.288c231a@ripper.onstor.net>
In-Reply-To: <200710101416.l9AEGJl02081@mailhost-rtp.css.glasshouse.com>
References: <200710101416.l9AEGJl02081@mailhost-rtp.css.glasshouse.com>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 10 Oct 2007 15:17:45 +0100 "Alan Cooke"
<acooke@css.glasshouse.com> wrote:

> Hi All,
> 
> Case 6092:
> 
> Customer DIR.bv is an ISP in Bulgaria.
> 
> They have  a 3 node cluster and have Debian linux clients running
> Debian "Lenny" whatever release that is.

Heh.  Lenny is the next release.  The current stable release of Debian
is 'Etch' [All the names come from characters in _Toy Story_].  In any
case, I believe Lenny is using a 2.6.22 based kernel, which is the main
thing here.

> They are getting various error messages they are concerned about.
> 
> From the Bobcats they are getting:
> 
>  
> 
> Oct 9 10:02:08 dir-nfs-2 : 1:1:unused:WARNING: 5019: rpc: program
> 100021 not registered on 10.100.0.82
> 
>  
> 
> From the Onstor wiki for this I find
> 
>  
> 
> NLM 100021 Classify up to NLM version and command type and mark as
> slow path in RX Descriptor.

I'm not sure what this means at all, but doesn't seem to be related.

> So presumably this is a process the Onstor wants to see that the linux
> client does not have a response to?

I'll have to leave this one to one of our RPC experts.

> Another set of error messages:
> 
>  
> 
> From the client they are getting:
> 
> Oct 8 10:14:16 www8 kernel: rpcbind: server 10.100.0.157 not
> responding, timed out 
> Oct 8 10:14:19 www8 kernel: nfs: server 10.100.0.157 not responding,
> still trying 
> Oct 8 10:14:27 www8 kernel: lockd: server 10.100.0.157 OK 
> Oct 8 10:14:27 www8 kernel: nfs: server 10.100.0.157 OK 
> Oct 8 10:14:27 www8 kernel: lockd: server 10.100.0.157 OK 
> Oct 8 10:14:30 www8 last message repeated 14 times 
> Oct 8 10:15:38 www8 kernel: lockd: server 10.100.0.157 not
> responding, still trying 
> Oct 8 10:15:57 www8 last message repeated 15 times 
> Oct 8 10:16:48 www8 kernel: lockd: server 10.100.0.157 OK 
> Oct 8 10:16:48 www8 last message repeated 15 times 
> Oct 8 10:19:23 www8 kernel: lockd: weird return 9 for CANCEL call 
> Oct 8 10:19:24 www8 last message repeated 32 times
> 
>  
> 
> I have done a search on the web for "lockd: weird return 9" and get a
> few non Debian ( suse ) hits but nothing I can make any sense from.

It's not a distro issue, but rather a kernel issue, and possibly an
issue with the version of nfs-utils that is being used.

> Can anyone help with these please?

I think we need to get a trace of the network traffic.  Can that be
obtained?  I'm using a 2.6.22 kernel myself and I don't get these
errors.  Also, what version of EverON is the filer running?

Cheers,

a
