From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Knecht Subject: Re: Possible to change chunk size on RAID-1 without re-init or destructive result? Date: Sun, 31 Mar 2013 10:56:56 -0700 Message-ID: References: <16639206.20.1364400094382.JavaMail.root@zimbra> <51534450.8050905@hardwarefreak.com> <51535252.2080105@hardwarefreak.com> <51536DDD.5010800@hardwarefreak.com> <51585CB9.5020208@hardwarefreak.com> <51587548.3060306@hardwarefreak.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <51587548.3060306@hardwarefreak.com> Sender: linux-raid-owner@vger.kernel.org To: Stan Hoeppner Cc: Roy Sigurd Karlsbakk , Jeff Johnson , Linux-RAID List-Id: linux-raid.ids On Sun, Mar 31, 2013 at 10:41 AM, Stan Hoeppner wrote: > On 3/31/2013 12:15 PM, Mark Knecht wrote: >> >> Hopefully that gives you enough info to suggest a direction. > > These applications append small data slowly over a long period of time, > which usually means fragmentation. Thus there's not much to optimize at > the chunk/stripe level, other than keeping chunk size small to spread > random reads over all platters. You currently have a 16KB chunk, IIRC, > which is about as good as you'll get for this workload. Given your > applications' low write throughput chunk/strip really doesn't matter. > > -- > Stan > OK, I cannot argue with your conclusions and will stick with 16K for now. Presumably if any improvement is to be made here its getting everything onto a single partition instead of multiple RAIDs on the same drives which then reduces the physical overhead (moving heads to different partitions) and allows the md software to do the heavy lifting? Thanks, Mark