From: Russell Coker <russell@coker.com.au>
To: linux-btrfs@vger.kernel.org, Qu Wenruo <wqu@suse.com>
Subject: Re: strangely uncorrectable errors with RAID-5
Date: Fri, 14 Mar 2025 23:27:51 +1100 [thread overview]
Message-ID: <1924801.tdWV9SEqCh@xev> (raw)
In-Reply-To: <0bedb9d8-0924-4c19-a5d1-9951b04f2781@suse.com>
On Monday, 21 October 2024 15:26:19 AEDT Qu Wenruo wrote:
> With the recent RAID56 improves, I'd say RAID5 data + RAID1 metadata is
> usable, but I'm not sure how it will survive in a production environment.
>
> Considering we have a lot of other problems out of our control, like bad
> disk flush behavior, and even hardware memory bitflips, I won't
> recommend RAID5 data for now, but I believe RAID56 for data has improved
> a lot.
>
> If you want to experiment RAID1 metadata with RAID5 data and report
> back, I would appreciate the effort a lot.
> And from my last work on RAID56 (for data), it should survive your
> random corruption script.
Just to see if anything had changed I ran the same tests with RAID-5 data and
metadata again with the Debian kernel 6.12.17-amd64 and this time got properly
uncorrectable errors in less than a minute. I don't know if the error
happened faster and worse than before because of some kernel difference, luck,
or some timing difference when running on different hardware.
The system is a Dell PowerEdge T630 with advanced ECC enabled so I don't think
that memory bitflips are an issue here.
[ 398.486860] BTRFS warning (device vdc): checksum error at logical
5073338368 on dev /dev/vdc, physical 1705771008: metadata leaf (level 0) in
tree 5
[ 398.487367] BTRFS error (device vdc): unable to fixup (regular) error at
logical 5073338368 on dev /dev/vdc physical 1705771008
[ 398.487826] BTRFS warning (device vdc): checksum error at logical
5073338368 on dev /dev/vdc, physical 1705771008: metadata leaf (level 0) in
tree 5
[ 398.488333] BTRFS error (device vdc): unable to fixup (regular) error at
logical 5073338368 on dev /dev/vdc physical 1705771008
[ 398.488792] BTRFS warning (device vdc): checksum error at logical
5073338368 on dev /dev/vdc, physical 1705771008: metadata leaf (level 0) in
tree 5
[ 398.489308] BTRFS error (device vdc): unable to fixup (regular) error at
logical 5073338368 on dev /dev/vdc physical 1705771008
[ 398.489772] BTRFS warning (device vdc): checksum error at logical
5073338368 on dev /dev/vdc, physical 1705771008: metadata leaf (level 0) in
tree 5
[ 398.490459] BTRFS error (device vdc): unable to fixup (regular) error at
logical 5073338368 on dev /dev/vdc physical 1705771008
[ 398.490926] BTRFS warning (device vdc): checksum error at logical
5073338368 on dev /dev/vdc, physical 1705771008: metadata leaf (level 0) in
tree 5
[ 398.491435] BTRFS error (device vdc): unable to fixup (regular) error at
logical 5073338368 on dev /dev/vdc physical 1705771008
[ 398.491898] BTRFS warning (device vdc): checksum error at logical
5073338368 on dev /dev/vdc, physical 1705771008: metadata leaf (level 0) in
tree 5
[ 398.492406] BTRFS error (device vdc): unable to fixup (regular) error at
logical 5073338368 on dev /dev/vdc physical 1705771008
[ 398.492868] BTRFS warning (device vdc): checksum error at logical
5073338368 on dev /dev/vdc, physical 1705771008: metadata leaf (level 0) in
tree 5
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2025-03-14 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 10:09 strangely uncorrectable errors with RAID-5 Russell Coker
2024-10-20 21:01 ` Qu Wenruo
2024-10-21 3:55 ` Russell Coker
2024-10-21 4:26 ` Qu Wenruo
2025-03-14 12:27 ` Russell Coker [this message]
2025-03-14 16:54 ` Russell Coker
2025-03-14 19:32 ` Thiago Ramon
2025-03-15 2:51 ` Russell Coker
2025-03-15 5:19 ` Andrei Borzenkov
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=1924801.tdWV9SEqCh@xev \
--to=russell@coker.com.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox