xfs
[Top] [All Lists]

Re: xfs crash bt (was: RE: ADD 804570 - The elevator bug)

To: Tony Gale l <gale@xxxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
Subject: Re: xfs crash bt (was: RE: ADD 804570 - The elevator bug)
From: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Wed, 06 Dec 2000 13:38:53 -0600
References: <XFMail.20001206180254.gale@xxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
Tony Gale wrote:

> On 06-Dec-2000 Russell Cattelan wrote:
> >
> > Well nothing obvious jumps out at me here, other than a possible
> > deadlock problem.
> >
> > Looking at the code related to the backtraces I don't see a common
> > lock
> > that
> > might be tripping us up.
> >
> > In the backtrace; find_inode is that  last  function listed?
>
> Well, it's first one listed, but yes.
>
> >
> > We probably need to look at the process table and find out what is
> > running and what might be stuck.
>
> I believe the two process stuck are expire (from inn) and slocate.
> Both of these would hit the fs pretty hard.
>
> I don't know the code, but could it be a resource starvation problem,
> such as out of inodes in the vfs?
>
> >
> > continue the system "go"
> > break it again and do the cpu back traces.
>
> Still stuck in the same places (with minor find_inode offset diff).

This may not be a lock contention problem then, it's possible we are
looping
on something? waiting for some resource?

Did you ever turn down the numbers in the elevator?

Try:
elvtune -r 1024 <dev>
elvtune -w 2048 <dev>

>
>
> >
> > Is is possible to get a serial console hooked up?
> > I would help a great deal in capturing  kdb output.
> >
> >
>
> Ok, will do so tomorrow, and then try and force a lockup (it's
> getting late to be at work here).
>
> Thanks
>
> -tony
>
> ---
> E-Mail: Tony Gale <gale@xxxxxxxxxxxxxxxxxx>
> Two wrongs are only the beginning.
>                 -- Kohn
>
> The views expressed above are entirely those of the writer
> and do not represent the views, policy or understanding of
> any other person or official body.


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