xfs
[Top] [All Lists]

Re: xfs deadlock on buffer semaphore while reading directory

To: Linda Walsh <xfs@xxxxxxxxx>
Subject: Re: xfs deadlock on buffer semaphore while reading directory
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 6 Feb 2013 11:44:42 +1100
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <510E054B.2070500@xxxxxxxxx>
References: <20130202192007.GS30577@xxxxxxxxxxxxxxxxxx> <510D6EDE.1080409@xxxxxxx> <510E054B.2070500@xxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Sat, Feb 02, 2013 at 10:35:55PM -0800, Linda Walsh wrote:
> 
> 
> Mark Tinguely wrote:
> >On 02/02/13 13:20, Andi Kleen wrote:
> >>
> >>On a older 3.6-rc9 opensuse kernel I had the following deadlock with
> >
> >That looks like a hang fixed by the series:
> >
> >    http://oss.sgi.com/archives/xfs/2012-12/msg00071.html
> ----
> 
> That may be so -- I used to see things like that on some older
> kernels with random progs but with traces down in xfs..
> 
> Seemed to be rare and not cause problems....but don't notice those any
> more...
> 
> Odd thing about my current probs -- my current system has been
> up 12 days...but before that it had been up 43 days...
> 
> 
> I can't get the buffers to 'free' no matter what
> echo 3> /proc/sys/vm/drop_caches does nothing.

What buffers are you talking about? The deadlock is in metadata
buffer handling, which you can't directly see, and will never be
able to entirely free via drop caches.

if you are talking about what is reported by the "free" command,
then that number can be ignored as it is mostly meaningless for XFS
filesystems....

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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