From: Linda Walsh <xfs@tlinx.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs deadlock on buffer semaphore while reading directory
Date: Sat, 09 Feb 2013 18:04:52 -0800 [thread overview]
Message-ID: <51170044.1090707@tlinx.org> (raw)
In-Reply-To: <20130206004442.GS2667@dastard>
Dave Chinner wrote:
>> 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....
----
Actually was talking 'cache', not buffers... sorry,
which I thought was mostly fs-data that was "freeable" (mostly).
whereas because of the error in xfs_dump, I was concerned about
it taking up all free memory (whereas normally, it doesn't
matter).
but I was trying to use echo 3>/proc/sys/vm/drop_caches, but that
seemed to pretty much be ignored...
But after boot and new kernel w/new and different problems,
xfs_dump (the new version) works fine... ;)
Sorry for any confusion.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-02-10 2:05 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
2013-02-06 19:28 ` Linda Walsh
2013-02-10 2:04 ` Linda Walsh [this message]
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=51170044.1090707@tlinx.org \
--to=xfs@tlinx.org \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.