xfs
[Top] [All Lists]

Re: pagebuf_cleaner crash was Re: CVS 2.3 tree

To: Andi Kleen <ak@xxxxxxx>
Subject: Re: pagebuf_cleaner crash was Re: CVS 2.3 tree
From: Rajagopal Ananthanarayanan <ananth@xxxxxxx>
Date: Fri, 02 Jun 2000 11:14:22 -0700
Cc: Russell Cattelan <cattelan@xxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
References: <3936AC63.E38A4E6F@xxxxxxxxxxx> <20000601225718.A12013@xxxxxxxxxxxxxxxxxxx> <3936D18D.174640C@xxxxxxxxxxx> <20000602183216.A25979@xxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
Andi Kleen wrote:
> 
> On Thu, Jun 01, 2000 at 04:11:41PM -0500, Russell Cattelan wrote:
> > >
> > > to do that for the ``TAKE'' messages on the list? Then you could just
> > > click on a change to look at it.
> > >
> > > -Andi
> >
> > BTW did switching compilers help?
> 
> Seems I was too quick. Unpack works now, but the libc compilation with
> no CONFIG_KIOVEC_IO ended with a BUG in the page_cleaner_daemon
> (during a big ``ar'' run):
> 
> delalloc page 0xc101d370 with no extent

The most interesting thing would be find out the nature of the
extents in this inode/file. I don't know if this is reproducible,
but if you have xfsidbg & kdbm_pb modules loaded, then the following
info. would help.

kdb> page 0xc101d370
        [ ...]  address_space <address1>
kdb> md <address1>
        [ ... pick the inode (5th word in the dump) = address2 ... ]
kdb> inode <address2>
        [ ... shows the vnode ptr (address3) ...]
kdb> vnode <address3>
        [ ... shows the vnode pobj (address4) ... ]
kdb> xexlist <address4>
        [ the extents we want ]


--------------------------------------------------------------------------
Rajagopal Ananthanarayanan ("ananth")
Member Technical Staff, SGI.
--------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>