linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: "stan@hardwarefreak.com Hoeppner" <stan@hardwarefreak.com>,
	xfs <xfs@oss.sgi.com>
Subject: Re: relationship of nested stripe sizes, was: Question regarding XFS on LVM over hardware RAID.
Date: Mon, 3 Feb 2014 08:30:30 +1100	[thread overview]
Message-ID: <20140202213030.GQ2212@dastard> (raw)
In-Reply-To: <98961D3F-769D-44A9-98A8-FC7867893138@colorremedies.com>

On Sun, Feb 02, 2014 at 11:09:11AM -0700, Chris Murphy wrote:
> On Feb 1, 2014, at 2:44 PM, Stan Hoeppner <stan@hardwarefreak.com>
> wrote:
> > On 2/1/2014 2:55 PM, Chris Murphy wrote:
> >> On Feb 1, 2014, at 11:47 AM, Stan Hoeppner
> >> <stan@hardwarefreak.com> wrote:
> > When nesting stripes, the chunk size of the outer stripe is
> > -always- equal to the stripe width of each inner striped array,
> > as I clearly demonstrated earlier:
> 
> Except when it's hardware raid6, and software raid0, and the user
> doesn't know they need to specify the chunk size in this manner.
> And instead they use the mdadm default. What you're saying makes
> complete sense, but I don't think this is widespread knowledge or
> well documented anywhere that regular end users would know this by
> and large.

And that is why this is a perfect example of what I'd like to see
people writing documentation for.

http://oss.sgi.com/archives/xfs/2013-12/msg00588.html

This is not the first time we've had this nested RAID discussion,
nor will it be the last. However, being able to point ot a web page
or or documentation makes it a whole lot easier.....

Stan - any chance you might be able to spare an hour a week to write
something about optimal RAID storage configuration for XFS?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-02-02 21:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31  6:35 relationship of nested stripe sizes, was: Question regarding XFS on LVM over hardware RAID Chris Murphy
2014-02-01 18:47 ` Stan Hoeppner
2014-02-01 20:55   ` Chris Murphy
2014-02-01 21:44     ` Stan Hoeppner
2014-02-02 18:09       ` Chris Murphy
2014-02-02 21:30         ` Dave Chinner [this message]
2014-02-03  4:39           ` Stan Hoeppner
2014-02-03  5:24             ` Dave Chinner
2014-02-03  9:36               ` Stan Hoeppner
2014-02-03 21:54                 ` Dave Chinner
2014-02-04  7:06                   ` documentation framework [was Re: relationship of nested stripe sizes, was: Question regarding XFS on LVM over hardware RAID.] Dave Chinner
2014-02-03 10:50         ` relationship of nested stripe sizes, was: Question regarding XFS on LVM over hardware RAID Stan Hoeppner

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=20140202213030.GQ2212@dastard \
    --to=david@fromorbit.com \
    --cc=lists@colorremedies.com \
    --cc=stan@hardwarefreak.com \
    --cc=xfs@oss.sgi.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).