From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Gary L. Grobe" <gary@grobe.net>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: processes in D state too long too often
Date: Tue, 10 Feb 2009 11:02:58 -0500 [thread overview]
Message-ID: <20090210160258.GD29075@fieldses.org> (raw)
In-Reply-To: <W322075763216621234232313@webmail8>
On Tue, Feb 10, 2009 at 02:18:33AM +0000, Gary L. Grobe wrote:
>
> >>The more likely explanation is that you just switched to a more recent
> >>distro where "sync" (as opposed to "async") is the option. Depending on
> >>workload, "async" may improve performance a great deal, at the expense
> >>of possible data corruption on server reboot!
> >>
> >>If you're doing a lot of writing and using NFSv2, then switching to
> >>NFSv3 may give you performance close to the "async" performance without
> >>the corruption worries.
>
> Just a small update about our rollback I need to correct. Turns out our problem has been solved by going with the 2.6.20-r10 of the gentoo-sources patched kernel. Although gentoo marks this as unstable for amd64, it's working fine. I've made no other changes than going back a few versions on the kernel and adjusting the .config w/ the same settings.
>
> Tomorrow I'll likely give the next marked stable patched gentoo-sources kernel another try which was 2.6.24-r10 and recheck my configs and try to gather anything else I can gather from it.
Sounds good, thanks.
--b.
next prev parent reply other threads:[~2009-02-10 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 2:18 processes in D state too long too often Gary L. Grobe
2009-02-10 16:02 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 1:04 Gary L. Grobe
2009-02-10 16:02 ` J. Bruce Fields
2009-02-07 20:49 Gary L. Grobe
2009-02-09 21:27 ` J. Bruce Fields
2009-02-07 6:30 processes in D State " Gary L. Grobe
2009-02-07 6:45 ` Andrew Morton
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=20090210160258.GD29075@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@linux-foundation.org \
--cc=gary@grobe.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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