From: Roman Mamedov <rm@romanrm.net>
To: Ochi <ochi@arcor.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: RAID5 on SSDs - looking for advice
Date: Sun, 9 Oct 2022 16:42:06 +0500 [thread overview]
Message-ID: <20221009164206.39de4305@nvm> (raw)
In-Reply-To: <a502eed4-b164-278a-2e80-b72013bcfc4f@arcor.de>
On Sun, 9 Oct 2022 12:34:57 +0200
Ochi <ochi@arcor.de> wrote:
> 3. Are there any other known issues that come to mind regarding this
> particular setup, or do you have any other advice?
Keep in mind that Btrfs RAID5/6 are not currently recommended for use:
https://btrfs.readthedocs.io/en/latest/btrfs-man5.html#raid56-status-and-recommended-practices
If the NAS is backed up anyway, I suggest going with directory-level merge of
filesystems, such as MergerFS. If one SSD fails, you will need to restore only
the files which happened to be on that one, not redo the entire thing, as
would be the case with RAID0, Btrfs single profile, or LVM-based large block
device across all three.
Another alternative is mdadm RAID5 with Btrfs on top. But it feels like that
also has its own corner cases when it comes to sudden power losses, which may
result in the "parent transid failed" condition from Btrfs-side (not sure if
the recent PPL in mdadm fixes that).
--
With respect,
Roman
next prev parent reply other threads:[~2022-10-09 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 10:34 RAID5 on SSDs - looking for advice Ochi
2022-10-09 11:36 ` Qu Wenruo
2022-10-09 12:56 ` Ochi
2022-10-09 13:01 ` Forza
2022-10-09 13:16 ` Ochi
2022-10-09 14:33 ` Jorge Bastos
2023-02-06 2:34 ` me
2023-02-06 3:05 ` Qu Wenruo
2023-02-09 23:12 ` me
2023-02-09 23:23 ` Remi Gauvin
2022-10-09 11:42 ` Roman Mamedov [this message]
2022-10-09 13:12 ` Ochi
2022-10-09 13:44 ` waxhead
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=20221009164206.39de4305@nvm \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=ochi@arcor.de \
/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