linux-kernel - Re: processes in D state too long too often

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090210160258.GD29075@fieldses.org>
Date:	Tue, 10 Feb 2009 11:02:58 -0500
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	"Gary L. Grobe" <gary@...be.net>
Cc:	linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: processes in D state too long too often

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/