From: Dave Chinner <david@fromorbit.com>
To: Linda Walsh <xfs@tlinx.org>
Cc: xfs@oss.sgi.com
Subject: Re: xfs deadlock on buffer semaphore while reading directory
Date: Wed, 6 Feb 2013 11:44:42 +1100 [thread overview]
Message-ID: <20130206004442.GS2667@dastard> (raw)
In-Reply-To: <510E054B.2070500@tlinx.org>
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@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-06 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 19:20 xfs deadlock on buffer semaphore while reading directory Andi Kleen
2013-02-02 19:54 ` Mark Tinguely
2013-02-02 20:46 ` Andi Kleen
2013-02-05 23:59 ` Mark Tinguely
2013-02-03 6:35 ` Linda Walsh
2013-02-03 16:42 ` Stan Hoeppner
2013-02-06 0:44 ` Dave Chinner [this message]
2013-02-06 19:28 ` Linda Walsh
2013-02-10 2:04 ` Linda Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130206004442.GS2667@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox