btrfs RAID5 or btrfs on md RAID5?
I have 4 x 4 TB SAS SSD (from a deactivated Netapp system) which I want to recycle in my workstation PC (Ubuntu 24 with kernel 6.14).
Is btrfs RAID5 ready for production usage or shall I use non-RAID btrfs on top of a md RAID5?
What is the current status?
Signature · 6 lines
Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: [email protected] Allmandring 30a Tel: ++49-711-68565868 70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/ REF:<[email protected]>
Quoted 6 lines · Ulli Horlacher
I have 4 x 4 TB SAS SSD (from a deactivated Netapp system) which I want to recycle in my workstation PC (Ubuntu 24 with kernel 6.14).
Is btrfs RAID5 ready for production usage or shall I use non-RAID btrfs on top of a md RAID5?
Neither is perfect.
Btrfs RAID56 has no journal to protect against write hole. But has the ability to properly detect and rebuild corrupted data using data checksum.
Meanwhile MD raid56 has journal to protect against wirte hole, but has no checksum to know which data is correct or not.
Quoted 3 lines
What is the current status?
No extra work is done for btrfs RAID56 write hole for a while.
The experimental raid-stripe-tree has some potential to address the problem, but that feature doesn't support RAID56 yet.
Another solution is something like RAIDZ, which requires block size > page size support, and extra RAID56 changes (mostly much smaller stripe length, 4K instead of the current 64K).
The bs > ps support is not even merged, and submitted patchset lacks certain features (RAID56 ironically). And no formal RAIDZ support is even considered.
So you either run RAID5 for data only and ran full scrub after every unexpected power loss (slow, and no further writes until scrub is done, which is further maintanance burden). Or just don't use RAID5 at all.
Thanks,
Qu
Quoted 4 lines · Qu Wenruo
Quoted 2 lines
Is btrfs RAID5 ready for production usage or shall I use non-RAID btrfs on top of a md RAID5?
Neither is perfect.
We live in a non-perfect world :-}
Quoted 1 line
Btrfs RAID56 has no journal to protect against write hole.
What does this mean?
What is a write hole and want is the danger with it?
Quoted 1 line
So you either run RAID5 for data only
This is a mkfs.btrfs option?
Shall I use "mkfs.btrfs -m dup" or "mkfs.btrfs -m raid1"?
Quoted 2 lines
and ran full scrub after every unexpected power loss (slow, and no further writes until scrub is done, which is further maintanance burden).
Ubuntu has (like most Linux distributions) systemd.
How can I detect a previous power loss and force full scrub on booting?
Quoted 1 line
Or just don't use RAID5 at all.
You suggest btrfs RAID0?
As I wrote: I have 4 x 4 TB SAS SSD (enterprise hardware, very reliable).
Another disk layout option for me could be:
64 GB / filesystem RAID1
32 GB swap RAID1
3.9 TB /home
3.9 TB /data
3.9 TB /VM
3.9 TB /backup
In case of a SSD damage failure I have to recover from (external) backup.
Signature · 6 lines
Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: [email protected] Allmandring 30a Tel: ++49-711-68565868 70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/ REF:<[email protected]>
Quoted 7 lines · Ulli Horlacher
Quoted 4 lines · Qu Wenruo
Quoted 2 lines
Is btrfs RAID5 ready for production usage or shall I use non-RAID btrfs on top of a md RAID5?
Neither is perfect.
Quoted 7 lines
We live in a non-perfect world :-}
Quoted 1 line
Btrfs RAID56 has no journal to protect against write hole.
What does this mean?
What is a write hole and want is the danger with it?
Write-hole means during a partial stripe update, a power loss happened, the parity may be out-of-sync.
This means that stripe will not get the full protection of RAID5.
E.g. after that power loss one device is lost, then btrfs may not be able to rebuild the correct data.
Quoted 6 lines
Quoted 3 lines
So you either run RAID5 for data only
This is a mkfs.btrfs option?
Shall I use "mkfs.btrfs -m dup" or "mkfs.btrfs -m raid1"?
For RAID5, RAID1 is preferred for data.
Quoted 7 lines
Quoted 4 lines
and ran full scrub after every unexpected power loss (slow, and no further writes until scrub is done, which is further maintanance burden).
Ubuntu has (like most Linux distributions) systemd.
How can I detect a previous power loss and force full scrub on booting?
Not sure. You may dig into systemd docs to find that out.
Quoted 5 lines
Quoted 3 lines
Or just don't use RAID5 at all.
You suggest btrfs RAID0?
I'd suggest RAID10. But that means you're "wasting" half of your capacity.
Thanks,
Qu
Quoted 13 lines
As I wrote: I have 4 x 4 TB SAS SSD (enterprise hardware, very reliable).
Another disk layout option for me could be:
64 GB / filesystem RAID1
32 GB swap RAID1
3.9 TB /home
3.9 TB /data
3.9 TB /VM
3.9 TB /backupIn case of a SSD damage failure I have to recover from (external) backup.
Quoted 7 lines · Qu Wenruo
Write-hole means during a partial stripe update, a power loss happened, the parity may be out-of-sync.
This means that stripe will not get the full protection of RAID5.
E.g. after that power loss one device is lost, then btrfs may not be able to rebuild the correct data.
It must happens both, power loss and one device is lost? Then this is a more rare situation: unlikly, but not impossible.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
So you either run RAID5 for data only
This is a mkfs.btrfs option?
Shall I use "mkfs.btrfs -m dup" or "mkfs.btrfs -m raid1"?For RAID5, RAID1 is preferred for data.
Then the real usable capacity of this volume is only the half? With 4 x 4 TB disks I get 2 TB, in opposite to 3 TB with RAID5 data?
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
and ran full scrub after every unexpected power loss (slow, and no further writes until scrub is done, which is further maintanance burden).
Ubuntu has (like most Linux distributions) systemd.
How can I detect a previous power loss and force full scrub on booting?Not sure. You may dig into systemd docs to find that out.
So, no recommandition from you. Difficult situation :-}
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
Or just don't use RAID5 at all.
You suggest btrfs RAID0?
I'd suggest RAID10. But that means you're "wasting" half of your capacity.
Ok, it is a trade off...
Signature · 6 lines
Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: [email protected] Allmandring 30a Tel: ++49-711-68565868 70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/ REF:<[email protected]>
Quoted 15 lines · Ulli Horlacher
Quoted 7 lines · Qu Wenruo
Write-hole means during a partial stripe update, a power loss happened, the parity may be out-of-sync.
This means that stripe will not get the full protection of RAID5.
E.g. after that power loss one device is lost, then btrfs may not be able to rebuild the correct data.
It must happens both, power loss and one device is lost? Then this is a more rare situation: unlikly, but not impossible.
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
So you either run RAID5 for data only
This is a mkfs.btrfs option?
Shall I use "mkfs.btrfs -m dup" or "mkfs.btrfs -m raid1"?For RAID5, RAID1 is preferred for data.
Then the real usable capacity of this volume is only the half?
No, metadata is really a small part of the fs.
The majority of usable space really depends on the data profile.
If you use RAID1 metadata + RAID5 data, I believe only less than 10% of real space is used on RAID1, the remaining is still RAID5.
Unless you put tons of small files (smaller than 2K), then those files will be inlined into metadata and takes a lot of space...
Thanks,
Qu
Quoted 23 lines
With 4 x 4 TB disks I get 2 TB, in opposite to 3 TB with RAID5 data?
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
and ran full scrub after every unexpected power loss (slow, and no further writes until scrub is done, which is further maintanance burden).
Ubuntu has (like most Linux distributions) systemd.
How can I detect a previous power loss and force full scrub on booting?Not sure. You may dig into systemd docs to find that out.
So, no recommandition from you. Difficult situation :-}
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
Or just don't use RAID5 at all.
You suggest btrfs RAID0?
I'd suggest RAID10. But that means you're "wasting" half of your capacity.
Ok, it is a trade off...
Resuming this discussion...
Quoted 7 lines · Qu Wenruo
Quoted 7 lines
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
So you either run RAID5 for data only
This is a mkfs.btrfs option?
Shall I use "mkfs.btrfs -m dup" or "mkfs.btrfs -m raid1"?For RAID5, RAID1 is preferred for data.
Quoted 8 lines
Quoted 1 line
Then the real usable capacity of this volume is only the half?
No, metadata is really a small part of the fs.
The majority of usable space really depends on the data profile.
If you use RAID1 metadata + RAID5 data, I believe only less than 10% of real space is used on RAID1, the remaining is still RAID5.
Sounds like a good compromise solution!
Asuming I have 4 partitions with equal size, then the suggested command to create the filesystem would be:
mkfs.btrfs -m raid1 -d raid5 /dev/sda4 /dev/sdb4 /dev/sdc4 /dev/sdd4
Does this setup help to protect against write hole?
Signature · 6 lines
Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: [email protected] Allmandring 30a Tel: ++49-711-68565868 70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/ REF:<[email protected]>
Quoted 22 lines · Ulli Horlacher
Resuming this discussion...
Quoted 7 lines · Qu Wenruo
Quoted 7 lines
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
So you either run RAID5 for data only
This is a mkfs.btrfs option?
Shall I use "mkfs.btrfs -m dup" or "mkfs.btrfs -m raid1"?For RAID5, RAID1 is preferred for data.
Quoted 8 lines
Quoted 1 line
Then the real usable capacity of this volume is only the half?
No, metadata is really a small part of the fs.
The majority of usable space really depends on the data profile.
If you use RAID1 metadata + RAID5 data, I believe only less than 10% of real space is used on RAID1, the remaining is still RAID5.
Quoted 9 lines
Sounds like a good compromise solution!
Asuming I have 4 partitions with equal size, then the suggested command to create the filesystem would be:
mkfs.btrfs -m raid1 -d raid5
/dev/sda4/dev/sdb4/dev/sdc4/dev/sdd4Does this setup help to protect against write hole?
No. It simply reduces the damage caused by the write hole. Only the content of individual files is affected, not the metadata.
Quoted 2 lines · Qu Wenruo
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.
Signature · 6 lines
Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: [email protected] Allmandring 30a Tel: ++49-711-68565868 70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/ REF:<[email protected]>
Quoted 11 lines · Ulli Horlacher
Quoted 2 lines · Qu Wenruo
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?
Yes.
Write-hole is only possible for RAID56 profiles which needs RMW.
RAID0/1/10 do not need RWM at all, thus they are completely safe.
Quoted 4 lines
Then this is could be the most robust solution for me. In case of a disk failure I have to recover from backup.
Are there any plans to work on either of the proposed solutions mentioned here to once and for all fix RAID56?
Quoted 36 lines · Qu Wenruo
Quoted 6 lines · Ulli Horlacher
I have 4 x 4 TB SAS SSD (from a deactivated Netapp system) which I want to recycle in my workstation PC (Ubuntu 24 with kernel 6.14).
Is btrfs RAID5 ready for production usage or shall I use non-RAID btrfs on top of a md RAID5?
Neither is perfect.
Btrfs RAID56 has no journal to protect against write hole. But has the ability to properly detect and rebuild corrupted data using data checksum.
Meanwhile MD raid56 has journal to protect against wirte hole, but has no checksum to know which data is correct or not.
Quoted 3 lines
What is the current status?
No extra work is done for btrfs RAID56 write hole for a while.
The experimental raid-stripe-tree has some potential to address the problem, but that feature doesn't support RAID56 yet.
Another solution is something like RAIDZ, which requires block size > page size support, and extra RAID56 changes (mostly much smaller stripe length, 4K instead of the current 64K).
The bs > ps support is not even merged, and submitted patchset lacks certain features (RAID56 ironically). And no formal RAIDZ support is even considered.
So you either run RAID5 for data only and ran full scrub after every unexpected power loss (slow, and no further writes until scrub is done, which is further maintanance burden). Or just don't use RAID5 at all.
Thanks,
Qu
Quoted 1 line · DanglingPointer
Are there any plans to work on either of the proposed solutions mentioned here to once and for all fix RAID56?
The brutal truth is probably that RAID5/6 is an idea whose time has passed. Storage is cheap enough that it doesn't warrant the added latency, CPU time, and complexity.
If I had four 4TB drives I would probably go for RAID1 data and RAID1C4 metadata.
Quoted 38 lines · Qu Wenruo
Quoted 36 lines · Ulli Horlacher
Quoted 6 lines
I have 4 x 4 TB SAS SSD (from a deactivated Netapp system) which I want to recycle in my workstation PC (Ubuntu 24 with kernel 6.14).
Is btrfs RAID5 ready for production usage or shall I use non-RAID btrfs on top of a md RAID5?
Neither is perfect.
Btrfs RAID56 has no journal to protect against write hole. But has the ability to properly detect and rebuild corrupted data using data checksum.
Meanwhile MD raid56 has journal to protect against wirte hole, but has no checksum to know which data is correct or not.
Quoted 3 lines
What is the current status?
No extra work is done for btrfs RAID56 write hole for a while.
The experimental raid-stripe-tree has some potential to address the problem, but that feature doesn't support RAID56 yet.
Another solution is something like RAIDZ, which requires block size > page size support, and extra RAID56 changes (mostly much smaller stripe length, 4K instead of the current 64K).
The bs > ps support is not even merged, and submitted patchset lacks certain features (RAID56 ironically). And no formal RAIDZ support is even considered.
So you either run RAID5 for data only and ran full scrub after every unexpected power loss (slow, and no further writes until scrub is done, which is further maintanance burden). Or just don't use RAID5 at all.
Thanks,
Qu
Quoted 5 lines · Mark Harmstone
The brutal truth is probably that RAID5/6 is an idea whose time has passed.
Storage is cheap enough that it doesn't warrant the added latency, CPU time,
and complexity.
That doesn't seem to be generally the case. We have e.g. large storage servers with 24x 22 TB HDDs.
RAID6 is plenty enough redundancy for these, loosing 2 HDDs. RAID1 would loose half.
Cheers,
Chris.
Christoph Anton Mitterer kirjoitti 21.10.2025 klo 18.53:
Quoted 7 lines · Mark Harmstone
Quoted 5 lines
The brutal truth is probably that RAID5/6 is an idea whose time has passed.
Storage is cheap enough that it doesn't warrant the added latency, CPU time,
and complexity.
Quoted 5 lines
That doesn't seem to be generally the case. We have e.g. large storage servers with 24x 22 TB HDDs.
RAID6 is plenty enough redundancy for these, loosing 2 HDDs. RAID1 would loose half.
Also significant, RAID1 only protects from single drive failure, RAID6 from two.
-JLarja
Quoted 10 lines · Christoph Anton Mitterer
Quoted 5 lines · Mark Harmstone
The brutal truth is probably that RAID5/6 is an idea whose time has passed.
Storage is cheap enough that it doesn't warrant the added latency, CPU time,
and complexity.That doesn't seem to be generally the case. We have e.g. large storage servers with 24x 22 TB HDDs.
Quoted 6 lines
RAID6 is plenty enough redundancy for these, loosing 2 HDDs. RAID1 would loose half.
Cheers,
Chris.
So for every sector you want to write, you actually need to write three and read 21. That seems a very quick way to wear out all those disks. And then one starts operating more slowly, which slows down every write...
I'd still use RAID1 in this case.
Quoted 11 lines · Mark Harmstone
Quoted 10 lines · Christoph Anton Mitterer
Quoted 5 lines · Mark Harmstone
The brutal truth is probably that RAID5/6 is an idea whose time has passed.
Storage is cheap enough that it doesn't warrant the added latency, CPU time,
and complexity.That doesn't seem to be generally the case. We have e.g. large storage servers with 24x 22 TB HDDs.
Quoted 8 lines
Quoted 6 lines
RAID6 is plenty enough redundancy for these, loosing 2 HDDs. RAID1 would loose half.
Cheers,
Chris.So for every sector you want to write, you actually need to write three and read 21.
RAID5 needs to read 2 sectors and write 2 sectors. Independently of the number of disks in the array.
It is more difficult to make any generic statement about RAID6 because to my best knowledge there is no standard parity computation algorithm for it, each vendor does something different. But simply adding the second parity block means you need to read 3 and write 3 blocks.
Quoted 5 lines
That seems a very quick way to wear out all those disks.
And then one starts operating more slowly, which slows down every write...I'd still use RAID1 in this case.
Quoted 16 lines · Andrei Borzenkov
Quoted 15 lines · Mark Harmstone
Quoted 14 lines · Christoph Anton Mitterer
Quoted 5 lines · Mark Harmstone
The brutal truth is probably that RAID5/6 is an idea whose time has passed.
Storage is cheap enough that it doesn't warrant the added latency, CPU time,
and complexity.That doesn't seem to be generally the case. We have e.g. large storage servers with 24x 22 TB HDDs.
RAID6 is plenty enough redundancy for these, loosing 2 HDDs. RAID1 would loose half.
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Cheers,
Chris.So for every sector you want to write, you actually need to write three and read 21.
RAID5 needs to read 2 sectors and write 2 sectors. Independently of the number of disks in the array.
This isn't the case for btrfs' implementation, which will stripe every chunk over each disk if it can. Possibly other people do something different.
Quoted 1 line
It is more difficult to make any generic statement about RAID6 because to my best knowledge there is no standard parity computation algorithm for it, each vendor does something different. But simply adding the second parity block means you need to read 3 and write 3 blocks.
Likewise for btrfs' implementation of RAID6. I suppose this shows that if anyone were ever to fix it, they would need to make sure that RAID6 chunks get given 4 stripes rather than 24.
Quoted 6 lines
Quoted 5 lines
That seems a very quick way to wear out all those disks.
And then one starts operating more slowly, which slows down every write...I'd still use RAID1 in this case.
Quoted 15 lines · Mark Harmstone
Quoted 14 lines · Christoph Anton Mitterer
Quoted 5 lines · Mark Harmstone
The brutal truth is probably that RAID5/6 is an idea whose time has passed.
Storage is cheap enough that it doesn't warrant the added latency, CPU time,
and complexity.That doesn't seem to be generally the case. We have e.g. large storage servers with 24x 22 TB HDDs.
RAID6 is plenty enough redundancy for these, loosing 2 HDDs. RAID1 would loose half.
Quoted 5 lines
Quoted 2 lines
Cheers,
Chris.So for every sector you want to write, you actually need to write three and read 21. That seems a very quick way to wear out all those disks. And then one starts operating more slowly, which slows down every write...
Yes, it is true that the classic raid5/6 doesn't scale well when the number of disks grows.
However I still think that there is room to a different approach. Like putting the redundancy inside the extent to avoid an RMW cycles. This and the fact that in BTRFS the extents are immutable, would avoid the slowness that you mention.
Quoted 2 lines
I'd still use RAID1 in this case.
This is faster, but also doesn't scale well (== expensive) when the storage
size grows.
BR
G.Baroncelli
Signature · 2 lines
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
Just going back to the original question I posted...
Will the BTRFS project decide to fix once and for all RAID56 to fix the write-hole even if the result is a slower-latent result?
At least that would be a fully functional production ready offering as version 1.0?
Future optimisations and improvements on that version 1.0 will obviously happen for the life of BTRFS and linux which will improve the performance from the impact of adding whatever is needed to fix the write-hole. Just like everything else! At least everyone can say it is done, although slower now! But feature complete! Making it faster will then incrementally happen as it evolves like everything else.
Quoted 38 lines · Goffredo Baroncelli
Quoted 15 lines · Mark Harmstone
Quoted 14 lines · Christoph Anton Mitterer
Quoted 5 lines · Mark Harmstone
The brutal truth is probably that RAID5/6 is an idea whose time has passed.
Storage is cheap enough that it doesn't warrant the added latency, CPU time,
and complexity.That doesn't seem to be generally the case. We have e.g. large storage servers with 24x 22 TB HDDs.
RAID6 is plenty enough redundancy for these, loosing 2 HDDs. RAID1 would loose half.
Quoted 5 lines
Quoted 2 lines
Cheers,
Chris.So for every sector you want to write, you actually need to write three and read 21. That seems a very quick way to wear out all those disks. And then one starts operating more slowly, which slows down every write...
Yes, it is true that the classic raid5/6 doesn't scale well when the number of disks grows.
However I still think that there is room to a different approach. Like putting the redundancy inside the extent to avoid an RMW cycles. This and the fact that in BTRFS the extents are immutable, would avoid the slowness that you mention.
Quoted 2 lines
I'd still use RAID1 in this case.
This is faster, but also doesn't scale well (== expensive) when the storage size grows.
BR
G.Baroncelli
Quoted 8 lines · On Mon, 22 Sep 2025 09:09:56 +0200 Ulli Horlacher…
I have 4 x 4 TB SAS SSD (from a deactivated Netapp system) which I want to recycle in my workstation PC (Ubuntu 24 with kernel 6.14).
Is btrfs RAID5 ready for production usage or shall I use non-RAID btrfs on top of a md RAID5?
What is the current status?
Hi,
md RAID5 with Partial Parity Log is perfect for btrfs:
https://www.kernel.org/doc/html/latest/driver-api/md/raid5-ppl.html
When a stripe is partially updated with new data, PPL ensures that the old data in the stripe will not be corrupted by the write-hole. The new data on the other hand is still affected by the write hole, but for btrfs that is not a problem.
Regards,
Lukas
Quoted 2 lines · Lukas Straub
md RAID5 with Partial Parity Log is perfect for btrfs:
https://www.kernel.org/doc/html/latest/driver-api/md/raid5-ppl.html
I already have another system with btrfs on top of md RAID5 (4 x 1.6 TB SSD):
root@juhu:~# uname -a Linux juhu 6.8.0-83-generic #83~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 9 18:19:47 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
root@juhu:~# mount | grep local /dev/md127 on /local type btrfs (rw,relatime,space_cache,user_subvol_rm_allowed,subvolid=5,subvol=/)
root@juhu:~# mdadm --detail /dev/md127
/dev/md127:
Version : 1.2
Creation Time : Thu Feb 10 09:38:22 2022
Raid Level : raid5
Array Size : 4285387776 (3.99 TiB 4.39 TB)
Used Dev Size : 1428462592 (1362.29 GiB 1462.75 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistentIntent Bitmap : Internal
Update Time : Mon Sep 22 10:43:43 2025
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : bitmap
Name : mux:nts1
UUID : 74388db3:3c3b30c3:e1295cc5:46f23ff7
Events : 23359
Number Major Minor RaidDevice State
0 8 20 0 active sync /dev/sdb4
1 8 4 1 active sync /dev/sda4
2 8 52 2 active sync /dev/sdd4
4 8 36 3 active sync /dev/sdc4
Shall I enable PPL there with mdadm --consistency-policy=ppl /dev/md127 ?
Signature · 6 lines
Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: [email protected] Allmandring 30a Tel: ++49-711-68565868 70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/ REF:<20250922100715.7f847dc0@penguin>