All of lore.kernel.org
 help / color / mirror / Atom feed
From: "D.S. Ljungmark" <spider@skuggor.se>
To: doug@easyco.com
Cc: linux-raid@vger.kernel.org
Subject: Re: md-raid and block sizes
Date: Tue, 28 Dec 2010 09:46:20 +0100	[thread overview]
Message-ID: <1293525980.23780.2.camel@Waves.darkmere> (raw)
In-Reply-To: <AANLkTikWxCxVUO+O8MXRXRR7Y8R5xGC1Catv-EiNGcDj@mail.gmail.com>

Thankyou, 
  This makes planning ahead a bit easier, and means that I "only" have
to worry about the traditional issues regarding block sizes, stripe and
stride on "naked" disks in the array. 

Regards,
   Spid

On Mon, 2010-12-27 at 10:59 -0800, Doug Dumitru wrote:
> Mr. Ljungmark,
> 
> The meta data is stored at the end of each raid device.  So if you are
> dealing with an "advanced partitioned" device, just make sure your
> individual elements are stores with alignments that make sense.  Normally,
> this is just 'fdisk -u' and start the partition on a multiple of 8 sectors
> (start at 64).
> 
> In terms of stripe sizes, they are all multiples of 4K pages anyway, so it
> is not really possible for them to be "wrong" in terms of drive format
> alignment.
> 
> File systems should be 4K or multiples thereof.  It has been a while, but I
> think only XFS really breaks this rule unless you overwrite the block size
> to 4K.  extn is fine.
> 
> The same rules apply to most SSDs.  Most SSDs prefer 4K alignment because of
> how the FTL (Flash Translation Layers) operate, even though <4K will
> sometimes still work pretty well.
> 
> Doug Dumitru
> CTO EasyCo LLC
> 
> On Mon, Dec 27, 2010 at 4:00 AM, D.S. Ljungmark <spider@skuggor.se> wrote:
> 
> > Hello,
> >  With the advent of the WD*EARS drives and the "advanced partitioning"
> > system that requires 4k blocks, I wanted to pop a quick question to see
> > how the md metadata is aligned and how it should be aligned to get
> > proper performance out of the devices.
> >
> > So, For raid1,  I'll assume there is some metadata-overhead on the
> > drives, how large is this block? Will there be need to make a partition
> > on the md-device in order to get proper alignment of filesystem =>
> > platters?
> >
> > for both raid1 and 5/6 levels, what are the appropiate stride-sizes for
> > ext3/4?
> >
> > For more advanced raid configurations (5-6), how should the ext3/4
> > stripe size be configured?
> >
> >
> > Yes, a lot of similarly naive questions, however, I'm asking mostly
> > because of how devices are changing from 512 to 4k sized blocks, with
> > quite interesting changes in performance, and I wanted to figure out
> > what is the current state of software raid. At which "level" of the
> > stack: (partition) raid (partition) filesystem ,  do you have to account
> > for the block sizes in order to not degrade performance of the devices.
> >
> > ( In a perfect world I'd be able to purchase a stack of the devices and
> > test for myself and come back with a report. However, money and hardware
> > is a scarce resource ;)
> >
> > ps.  please keep me CC'd as I'm not subscribed to the list.
> >
> >
> > // Spider
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> 
> 
> 



  parent reply	other threads:[~2010-12-28  8:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 12:00 md-raid and block sizes D.S. Ljungmark
2010-12-27 19:02 ` Doug Dumitru
2010-12-28 11:45   ` John Robinson
     [not found] ` <AANLkTikWxCxVUO+O8MXRXRR7Y8R5xGC1Catv-EiNGcDj@mail.gmail.com>
2010-12-28  8:46   ` D.S. Ljungmark [this message]
2010-12-28 11:29     ` hansbkk
2010-12-28 11:45       ` Neil Brown
2010-12-28 11:50         ` Mikael Abrahamsson
2010-12-28 11:51         ` Roman Mamedov
2010-12-28 11:45       ` Roman Mamedov

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=1293525980.23780.2.camel@Waves.darkmere \
    --to=spider@skuggor.se \
    --cc=doug@easyco.com \
    --cc=linux-raid@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.