From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Lukas Straub <lukasstraub2@web.de>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: RAID56 discussion related to RST. (Was "Re: [RFC ONLY 0/8] btrfs: introduce raid-stripe-tree")
Date: Wed, 13 Jul 2022 15:28:20 +0000 [thread overview]
Message-ID: <PH0PR04MB74169AEEDF78C8FCBCD30C0E9B899@PH0PR04MB7416.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20220713152424.0d93e5fd@gecko
On 13.07.22 17:25, Lukas Straub wrote:
>
> Have you considered variable stripe size? I believe ZFS does this.
> Should be easy for raid5 since it's just xor, not sure for raid6.
>
> PS: ZFS seems to do variable-_width_ stripes
> https://pthree.org/2012/12/05/zfs-administration-part-ii-raidz/
I did and coincidentally we have been talking about it just 5 minutes
ago and both David and Chris aren't very fond of the idea.
next prev parent reply other threads:[~2022-07-13 15:28 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 14:31 [RFC ONLY 0/8] btrfs: introduce raid-stripe-tree Johannes Thumshirn
2022-05-16 14:31 ` [RFC ONLY 1/8] btrfs: add raid stripe tree definitions Johannes Thumshirn
2022-05-17 7:39 ` Qu Wenruo
2022-05-17 7:45 ` Johannes Thumshirn
2022-05-17 7:56 ` Qu Wenruo
2022-05-16 14:31 ` [RFC ONLY 2/8] btrfs: move btrfs_io_context to volumes.h Johannes Thumshirn
2022-05-17 7:42 ` Qu Wenruo
2022-05-17 7:51 ` Johannes Thumshirn
2022-05-17 7:58 ` Qu Wenruo
2022-05-17 8:01 ` Johannes Thumshirn
2022-05-16 14:31 ` [RFC ONLY 3/8] btrfs: read raid-stripe-tree from disk Johannes Thumshirn
2022-05-17 8:09 ` Qu Wenruo
2022-05-17 8:13 ` Johannes Thumshirn
2022-05-17 8:28 ` Qu Wenruo
2022-05-18 11:29 ` Johannes Thumshirn
2022-05-19 8:36 ` Qu Wenruo
2022-05-19 8:39 ` Johannes Thumshirn
2022-05-19 10:37 ` Qu Wenruo
2022-05-19 11:44 ` Johannes Thumshirn
2022-05-19 11:48 ` Qu Wenruo
2022-05-19 11:53 ` Johannes Thumshirn
2022-05-19 13:26 ` Qu Wenruo
2022-05-19 13:49 ` Johannes Thumshirn
2022-05-19 22:56 ` Qu Wenruo
2022-05-20 8:27 ` Johannes Thumshirn
2022-05-16 14:31 ` [RFC ONLY 4/8] btrfs: add boilerplate code to insert raid extent Johannes Thumshirn
2022-05-17 7:53 ` Qu Wenruo
2022-05-17 8:00 ` Qu Wenruo
2022-05-17 8:05 ` Johannes Thumshirn
2022-05-17 8:09 ` Qu Wenruo
2022-05-16 14:31 ` [RFC ONLY 5/8] btrfs: add code to delete " Johannes Thumshirn
2022-05-17 8:06 ` Qu Wenruo
2022-05-17 8:10 ` Johannes Thumshirn
2022-05-17 8:14 ` Qu Wenruo
2022-05-17 8:20 ` Johannes Thumshirn
2022-05-17 8:31 ` Qu Wenruo
2022-05-16 14:31 ` [RFC ONLY 6/8] btrfs: add code to read " Johannes Thumshirn
2022-05-16 14:55 ` Josef Bacik
2022-05-16 14:31 ` [RFC ONLY 7/8] btrfs: zoned: allow zoned RAID1 Johannes Thumshirn
2022-05-16 14:31 ` [RFC ONLY 8/8] btrfs: add raid stripe tree pretty printer Johannes Thumshirn
2022-05-16 14:58 ` [RFC ONLY 0/8] btrfs: introduce raid-stripe-tree Josef Bacik
2022-05-16 15:04 ` Johannes Thumshirn
2022-05-16 15:10 ` Josef Bacik
2022-05-16 15:47 ` Johannes Thumshirn
2022-05-17 7:23 ` Nikolay Borisov
2022-05-17 7:31 ` Qu Wenruo
2022-05-17 7:41 ` Johannes Thumshirn
2022-05-17 7:32 ` Johannes Thumshirn
2022-07-13 10:54 ` RAID56 discussion related to RST. (Was "Re: [RFC ONLY 0/8] btrfs: introduce raid-stripe-tree") Qu Wenruo
2022-07-13 11:43 ` Johannes Thumshirn
2022-07-13 12:01 ` Qu Wenruo
2022-07-13 12:42 ` Johannes Thumshirn
2022-07-13 13:47 ` Qu Wenruo
2022-07-13 14:01 ` Johannes Thumshirn
2022-07-13 15:24 ` Lukas Straub
2022-07-13 15:28 ` Johannes Thumshirn [this message]
2022-07-14 1:08 ` Qu Wenruo
2022-07-14 7:08 ` Johannes Thumshirn
2022-07-14 7:32 ` Qu Wenruo
2022-07-14 7:46 ` Johannes Thumshirn
2022-07-14 7:53 ` Qu Wenruo
2022-07-15 17:54 ` Goffredo Baroncelli
2022-07-15 19:08 ` Thiago Ramon
2022-07-16 0:34 ` Qu Wenruo
2022-07-16 11:11 ` Qu Wenruo
2022-07-16 13:52 ` Thiago Ramon
2022-07-16 14:26 ` Goffredo Baroncelli
2022-07-17 17:58 ` Goffredo Baroncelli
2022-07-17 0:30 ` Qu Wenruo
2022-07-17 15:18 ` Thiago Ramon
2022-07-17 22:01 ` Qu Wenruo
2022-07-17 23:00 ` Zygo Blaxell
2022-07-18 1:04 ` Qu Wenruo
2022-07-15 20:14 ` Chris Murphy
2022-07-18 7:33 ` Johannes Thumshirn
2022-07-18 8:03 ` Qu Wenruo
2022-07-18 21:49 ` Forza
2022-07-19 1:19 ` Qu Wenruo
2022-07-21 14:51 ` Forza
2022-07-24 11:27 ` Qu Wenruo
2022-07-25 0:00 ` Zygo Blaxell
2022-07-25 0:25 ` Qu Wenruo
2022-07-25 5:41 ` Zygo Blaxell
2022-07-25 7:49 ` Qu Wenruo
2022-07-25 19:58 ` Goffredo Baroncelli
2022-07-25 21:29 ` Qu Wenruo
2022-07-18 7:30 ` Johannes Thumshirn
2022-07-19 18:58 ` Goffredo Baroncelli
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=PH0PR04MB74169AEEDF78C8FCBCD30C0E9B899@PH0PR04MB7416.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lukasstraub2@web.de \
--cc=quwenruo.btrfs@gmx.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 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.