From: Michael Tokarev <mjt@tls.msk.ru>
To: Wil Reichert <wil.reichert@gmail.com>
Cc: linux raid <linux-raid@vger.kernel.org>
Subject: Re: filesystem stripe parameters
Date: Sat, 20 Jun 2009 10:19:57 +0400 [thread overview]
Message-ID: <4A3C7F8D.2090609@msgid.tls.msk.ru> (raw)
In-Reply-To: <7a329d910906191726k7acde13ye5f3b3c2e76c6692@mail.gmail.com>
Wil Reichert wrote:
> On Fri, Jun 19, 2009 at 2:15 AM, Michael Tokarev<mjt@tls.msk.ru> wrote:
[]
>> When everything is properly aligned, it's still worth the effort
>> IMHO to tell the filesystem about true raid properties.
>
> Several questions answered, more questions arise =)
>
> I'm using 3 1T discs, so it seems I'm in luck. My chunk size is 128k,
> my PE size is the default 4M. Using mkfs.ext4 as an example, it takes
> stride (chunk) and stripe-width ( chunk * (N-1) ) parameters. So
> which would be optimal - using the RAID values (i.e. 128k, 256k) or
> the LVM values (i.e. 4M, 8M) when creating the filesystem or is there
> no right answer and it just depends on the usage pattern?
No, see my last statement from my initial email, quoted above.
Tell the fs about your raid. If raid strips are combined using
some other way it's still raid and it's still strip size that
matters much. After all, you need two parameters for the fs
(chunk + stripe-width) not one (lvm block size) -- this fact
already telling :)
/mjt
prev parent reply other threads:[~2009-06-20 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 19:08 filesystem stripe parameters Wil Reichert
2009-06-19 9:15 ` Michael Tokarev
2009-06-19 9:36 ` Robin Hill
2009-06-19 20:59 ` Justin Perreault
2009-06-20 6:35 ` Michael Tokarev
2009-06-20 0:26 ` Wil Reichert
2009-06-20 6:19 ` Michael Tokarev [this message]
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=4A3C7F8D.2090609@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-raid@vger.kernel.org \
--cc=wil.reichert@gmail.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).