From: Stan Hoeppner <stan@hardwarefreak.com>
To: Linda Walsh <xfs@tlinx.org>
Cc: xfs@oss.sgi.com
Subject: Re: xfs deadlock on buffer semaphore while reading directory
Date: Sun, 03 Feb 2013 10:42:26 -0600 [thread overview]
Message-ID: <510E9372.60808@hardwarefreak.com> (raw)
In-Reply-To: <510E054B.2070500@tlinx.org>
On 2/3/2013 12:35 AM, Linda Walsh wrote:
> Odd thing about my current probs -- my current system has been
> up 12 days...but before that it had been up 43 days...
Linux greer 3.2.6 #1 SMP Mon Feb 20 17:05:10 CST 2012 i686 GNU/Linux
10:13:13 up 339 days, 22:42, 1 user, load average: 0.06, 0.06, 0.05
This is a hand rolled 'minimalist' kernel with the old SLAB allocator,
no modules, Debian 6 atop. Just over 11 months of flawless operation,
though load is probably much lighter than on your system.
> I can't get the buffers to 'free' no matter what
> echo 3> /proc/sys/vm/drop_caches does nothing.
That's interesting.
> so I may be rebooting soon...
Did you roll this 3.7.1 yourself? I'm wondering if you did something
wonky in your config that's causing or contributing to your problems.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-03 16:42 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 [this message]
2013-02-06 0:44 ` Dave Chinner
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=510E9372.60808@hardwarefreak.com \
--to=stan@hardwarefreak.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