From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: john terragon <jterragon@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: is it safe to change BTRFS_STRIPE_LEN?
Date: Sat, 24 May 2014 15:07:35 -0400 [thread overview]
Message-ID: <5380EDF7.6010606@gmail.com> (raw)
In-Reply-To: <CANg_oxybdjtOXrqo=yLPEKEz=NrJtSRfGgMxDeCQP+0EAbV_Qw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
On 05/24/2014 12:44 PM, john terragon wrote:
> Hi.
>
> I'm playing around with (software) raid0 on SSDs and since I remember
> I read somewhere that intel recommends 128K stripe size for HDD arrays
> but only 16K stripe size for SSD arrays, I wanted to see how a
> small(er) stripe size would work on my system. Obviously with btrfs on
> top of md-raid I could use the stripe size I want. But if I'm not
> mistaken the stripe size with the native raid0 in btrfs is fixed to
> 64K in BTRFS_STRIPE_LEN (volumes.h).
> So I was wondering if it would be reasonably safe to just change that
> to 16K (and duck and wait for the explosion ;) ).
>
> Can anyone adept to the inner workings of btrfs raid0 code confirm if
> that would be the right way to proceed? (obviously without absolutely
> any blame to be placed on anyone other than myself if things should go
> badly :) )
I personally can't render an opinion on whether changing it would make
things break or not, but I do know that it would need to be changed both
in the kernel and the tools, and the resultant kernel and tools would
not be entirely compatible with filesystems produced by the regular
tools and kernel, possibly to the point of corrupting any filesystem
they touch.
As for the 64k default strip size, that sounds correct, and is probably
because that's the largest block that the I/O schedulers on Linux will
dispatch as a single write to the underlying device.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
next prev parent reply other threads:[~2014-05-24 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 16:44 is it safe to change BTRFS_STRIPE_LEN? john terragon
2014-05-24 19:07 ` Austin S Hemmelgarn [this message]
2014-05-24 20:01 ` john terragon
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=5380EDF7.6010606@gmail.com \
--to=ahferroin7@gmail.com \
--cc=jterragon@gmail.com \
--cc=linux-btrfs@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 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).