Re: NFS regression? Odd delays and lockups accessing an NFS export.

[Ian Campbell <ijc-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]

On Fri, 2008-08-22 at 14:23 -0700, Trond Myklebust wrote:
> On Fri, 2008-08-22 at 21:00 +0100, Ian Campbell wrote:
> > On Fri, 2008-08-22 at 12:33 -0700, John Ronciak wrote:
> > > On Fri, Aug 22, 2008 at 11:13 AM, Ian Campbell <ijc-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org> wrote:
> > > 
> > > >> That's probably also a networking device driver issue candidate: your
> > > >> RPC task is queued up waiting to be sent.
> > > >>
> > > >> What networking card+device driver are you using here?
> > > >
> > > > # ethtool -i eth0
> > > > driver: e1000
> > > > version: 7.3.20-k2-NAPI
> > > > firmware-version: N/A
> > > > bus-info: 0000:01:0a.0
> > > There is nothing indicating that the NIC/driver is causing any sort of
> > > problem here, at least not with what has been presented so far.  When
> > > the NFS mount isn't working is the networking still active and
> > > working?
> > 
> > So far as I can tell, yes. I can login via ssh so long as the user
> > doesn't have NFS $HOME, I haven't tried much else and the box isn't
> > locked up at the moment, I'd bet it's fine though.
> 
> ...and the server? Something is preventing that RPC payload from being
> delivered...

I can ssh to the server fine. The same server also serves my NFS home
directory to the box I'm writing this from and I've not seen any trouble
with this box at all, it's a 2.6.18-xen box.

If I downgrade the problematic box to 2.6.24 then the hangs do not
occur. They do occur with 2.6.25. (sorry that's a critical bit of
information which I stupidly forgot to mention up til now).

Ian.

-- 
Ian Campbell

It is much easier to be critical than to be correct.
		-- Benjamin Disraeli

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]