From: Sanidhya Solanki <jpage.lkml@gmail.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] BTRFS: Adds an option to select RAID Stripe size
Date: Mon, 28 Dec 2015 19:03:36 -0500 [thread overview]
Message-ID: <20151228190336.59a3f440@gmail.com> (raw)
In-Reply-To: <1451360528.7094.7.camel@scientia.net>
On Tue, 29 Dec 2015 04:42:08 +0100
Christoph Anton Mitterer <calestyo@scientia.net> wrote:
> On Mon, 2015-12-28 at 16:43 -0500, Sanidhya Solanki wrote:
> May get even much more complicated, if reshaping (i.e. conversion from
> one chunk size to another) should get implemented as well...
That sounds like an absolutely ghastly idea. Lots of potential for
mistakes and potential data loss. I take up the offer to implement
such a feature.
Only question is should it be in-place replacement or replace out to
another disk or storage type. Will wait for comments on that question
before implementing.
> Sure :)
> Being able to set the RAID chunk size makes AFAIU sense for every RAID
> level, depending which IO patterns one has (i.e. even for RAID1).
I do not understand this part. Is the stripe size not independent of
the RAID type? To me it would seem that the filesystem just treats the
RAID type as a means of duplicating (if in the case of a redundant
RAID) or parallelizing data (in case of "R"AID 0), as opposed to the
Stripe length, which is a measure of each logical block for the
filesystem.
Thanks.
next prev parent reply other threads:[~2015-12-29 4:05 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 12:24 [PATCH] BTRFS: Adds an option to select RAID Stripe size Sanidhya Solanki
2015-12-28 22:19 ` Christoph Anton Mitterer
2015-12-28 20:38 ` Sanidhya Solanki
2015-12-29 1:21 ` Christoph Anton Mitterer
2015-12-28 21:43 ` Sanidhya Solanki
2015-12-29 3:42 ` Christoph Anton Mitterer
2015-12-29 0:03 ` Sanidhya Solanki [this message]
2015-12-29 4:26 ` Christoph Anton Mitterer
2015-12-29 1:31 ` Sanidhya Solanki
2015-12-29 6:03 ` Christoph Anton Mitterer
2015-12-29 2:23 ` Sanidhya Solanki
2015-12-29 15:32 ` Christoph Anton Mitterer
2015-12-29 16:44 ` Duncan
2015-12-30 2:56 ` Christoph Anton Mitterer
2015-12-29 18:06 ` David Sterba
2015-12-30 20:00 ` Christoph Anton Mitterer
2015-12-30 21:02 ` Duncan
2015-12-30 21:13 ` Christoph Anton Mitterer
2016-01-02 11:52 ` Sanidhya Solanki
2016-01-03 1:37 ` Qu Wenruo
2016-01-03 2:26 ` Christoph Anton Mitterer
2016-01-05 10:44 ` David Sterba
2016-01-05 18:48 ` Christoph Anton Mitterer
2016-01-10 3:11 ` Sanidhya Solanki
2016-01-11 1:29 ` Qu Wenruo
2016-01-11 15:43 ` Christoph Anton Mitterer
2016-01-11 11:49 ` Sanidhya Solanki
2016-01-11 15:57 ` Christoph Anton Mitterer
2016-01-11 16:01 ` Hugo Mills
2016-01-12 12:23 ` Austin S. Hemmelgarn
2016-01-12 12:07 ` Sanidhya Solanki
2015-12-29 13:39 ` David Sterba
2015-12-29 11:15 ` Sanidhya Solanki
2015-12-29 17:06 ` David Sterba
2015-12-29 21:32 ` Sanidhya Solanki
2015-12-30 6:39 ` Sanidhya Solanki
2015-12-30 11:59 ` Qu Wenruo
2015-12-30 9:54 ` Sanidhya Solanki
2015-12-30 14:10 ` Qu Wenruo
2015-12-30 11:15 ` Sanidhya Solanki
2015-12-30 15:58 ` David Sterba
2015-12-30 21:19 ` Sanidhya Solanki
2015-12-30 16:17 ` David Sterba
2015-12-30 21:21 ` Sanidhya Solanki
2016-01-05 10:33 ` David Sterba
2015-12-31 0:46 ` Qu Wenruo
2016-01-05 10:16 ` David Sterba
2015-12-30 19:48 ` Christoph Anton Mitterer
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=20151228190336.59a3f440@gmail.com \
--to=jpage.lkml@gmail.com \
--cc=calestyo@scientia.net \
--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).