From: Kris Corwin <Kris.Corwin@hp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch 1/3] fix illogical behavior in balance_dirty_pages()
Date: Tue, 03 Apr 2007 14:40:03 -0400 [thread overview]
Message-ID: <46129F83.3070505@hp.com> (raw)
I think I'm seeing the same VM behavior with NFS/ext3 that was described
with fuse.
I have a shared storage unit with 2 servers. The local filesystem is
ext3 and I'm failing
the ext3 mounting and NFS serving from one node to another. I'm running
I/O on the NFS
mount point to the active server. If I failover to the server that is
also executing the I/O,
I can hang the machine. Looking at the stack traces, the NFS writes are
stuck in
balance_dirty_pages(). NFS start up is causing rpc.mountd to write to
the local
ext3 filesystem, but it gets blocked in balance_dirty_pages() too.
Deadlock. Without
the NFS server successfully started, the kernel can't write the dirty pages.
I'm running a 2.6.9-42 RH kernel. Early in my debugging, I had tried
several kernel
versions. All 2.6 kernels saw this behavior and the 2.4 kernel I tried
did not.
Kris Corwin
next reply other threads:[~2007-04-03 18:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 18:40 Kris Corwin [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-24 21:55 [patch 1/3] fix illogical behavior in balance_dirty_pages() Miklos Szeredi
2007-03-25 10:03 ` Peter Zijlstra
2007-03-25 11:12 ` Miklos Szeredi
2007-03-25 11:34 ` Miklos Szeredi
2007-03-25 11:50 ` Peter Zijlstra
2007-03-25 20:41 ` Miklos Szeredi
2007-03-25 23:35 ` Andrew Morton
2007-03-26 8:26 ` Miklos Szeredi
2007-03-26 9:01 ` Andrew Morton
2007-03-26 9:20 ` Miklos Szeredi
2007-03-26 9:32 ` Andrew Morton
2007-03-26 9:48 ` Miklos Szeredi
2007-03-26 9:32 ` Miklos Szeredi
2007-03-26 10:08 ` Andrew Morton
2007-03-26 13:30 ` Peter Zijlstra
2007-03-27 0:30 ` David Chinner
2007-03-27 0:23 ` David Chinner
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=46129F83.3070505@hp.com \
--to=kris.corwin@hp.com \
--cc=linux-kernel@vger.kernel.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