All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gary L. Grobe" <gary-QhKe0p0S2m1eoWH0uzbU5w@public.gmane.org>
To: "Gary L. Grobe" <gary-QhKe0p0S2m1eoWH0uzbU5w@public.gmane.org>,
	"J. Bruce Fields" <bfields@fieldses.org>
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 02:18:33 +0000	[thread overview]
Message-ID: <W322075763216621234232313@webmail8> (raw)


>>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.



WARNING: multiple messages have this Message-ID (diff)
From: "Gary L. Grobe" <gary@grobe.net>
To: "Gary L. Grobe" <gary@grobe.net>,
	"J. Bruce Fields" <bfields@fieldses.org>
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 02:18:33 +0000	[thread overview]
Message-ID: <W322075763216621234232313@webmail8> (raw)


>>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.



             reply	other threads:[~2009-02-10  2:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  2:18 Gary L. Grobe [this message]
2009-02-10  2:18 ` processes in D state too long too often Gary L. Grobe
2009-02-10 16:02 ` J. Bruce Fields
2009-02-10 16:02   ` J. Bruce Fields
  -- 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-10 16:02   ` J. Bruce Fields
2009-02-07 20:49 Gary L. Grobe
2009-02-07 20:49 ` Gary L. Grobe
2009-02-09 21:27 ` J. Bruce Fields
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
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=W322075763216621234232313@webmail8 \
    --to=gary-qhke0p0s2m1eowh0uzbu5w@public.gmane.org \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --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 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.