From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs RAID5 or btrfs on md RAID5?
Date: Mon, 22 Sep 2025 11:43:04 +0200 [thread overview]
Message-ID: <20250922094304.GB2634184@tik.uni-stuttgart.de> (raw)
In-Reply-To: <d3a5e463-d00e-4428-ad7b-35f87f9a6550@gmx.com>
On Mon 2025-09-22 (17:11), Qu Wenruo wrote:
> Btrfs RAID56 has no journal to protect against write hole. But has the
> ability to properly detect and rebuild corrupted data using data checksum.
As I wrote before, I could use btrfs RAID1 (only) for the / filesystem (64
GB), the other partitions without any RAID level, just simple btrfs
filesytems. No md RAID volumes at all.
btrfs RAID1 is not prone to write holes, but is able to rebuild corrupted
data using data checksum?
Then this is could be the most robust solution for me.
In case of a disk failure I have to recover from backup.
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/
REF:<d3a5e463-d00e-4428-ad7b-35f87f9a6550@gmx.com>
next prev parent reply other threads:[~2025-09-22 9:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 7:09 btrfs RAID5 or btrfs on md RAID5? Ulli Horlacher
2025-09-22 7:41 ` Qu Wenruo
2025-09-22 8:28 ` Ulli Horlacher
2025-09-22 9:06 ` Qu Wenruo
2025-09-22 9:23 ` Ulli Horlacher
2025-09-22 9:27 ` Qu Wenruo
2025-10-20 9:00 ` Ulli Horlacher
2025-10-20 9:31 ` Andrei Borzenkov
2025-09-22 9:43 ` Ulli Horlacher [this message]
2025-09-22 10:41 ` Qu Wenruo
2025-10-21 1:02 ` DanglingPointer
2025-10-21 15:46 ` Mark Harmstone
2025-10-21 15:53 ` Christoph Anton Mitterer
2025-10-21 16:15 ` Jukka Larja
2025-10-21 16:45 ` Mark Harmstone
2025-10-21 17:32 ` Andrei Borzenkov
2025-10-21 17:43 ` Mark Harmstone
2025-10-21 19:32 ` Goffredo Baroncelli
2025-10-21 22:19 ` DanglingPointer
2025-09-22 8:07 ` Lukas Straub
2025-09-22 8:50 ` Ulli Horlacher
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=20250922094304.GB2634184@tik.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--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).