From: Christoph Hellwig Subject: Re: Filesystem writes on RAID5 too slow Date: Sat, 23 Nov 2013 00:41:06 -0800 Message-ID: <20131123084106.GA19088@infradead.org> References: <528A5C45.4080906@redhat.com> <20131119005740.GY6188@dastard> <20131121092606.GU11434@dastard> <20131121234116.GD6502@dastard> <20131122092136.GD32568@infradead.org> <20131122224038.GH6502@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , Martin Boutin , "Kernel.org-Linux-RAID" , Eric Sandeen , "Kernel.org-Linux-EXT4" , xfs-oss To: Dave Chinner Return-path: Received: from bombadil.infradead.org ([198.137.202.9]:57387 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751311Ab3KWIlI (ORCPT ); Sat, 23 Nov 2013 03:41:08 -0500 Content-Disposition: inline In-Reply-To: <20131122224038.GH6502@dastard> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Sat, Nov 23, 2013 at 09:40:38AM +1100, Dave Chinner wrote: > > geometry, and we already have it wired to to large sector size > > testing in xfstests. > > We don't need to screw around with the sector size - that is > irrelevant to the problem, and we have an allocation alignment > test that is supposed to catch these issues: generic/223. It didn't imply we need large sector sizes, but the same mechanism to expodse a large sector size can also be used to present large stripe units/width. > As I said, I have seen occasional failures of that test (once a > month, on average) as a result of this bug. It was simply not often > enough - running in a hard loop didn't increase the frequency of > failures - to be able debug it or to reach my "there's a regression > I need to look at" threshold. Perhaps we need to revisit that test > and see if we can make it more likely to trigger failures... Seems like 233 should have cought it regularly with the explicit alignment options on mkfs time. Maybe we also need a test mirroring the plain dd more closely? I've not seen 233 fail for a long time..