Does Linux-6.12 have the missing dev = single/degraded chunk bug?
Hi,
I'm reviewing documentation of outstanding bugs and workarounds, and I'm wondering what the state of the single/degraded chunk bug is for Linux-6.12.
Specifically, I seem to remember that the users/sysadmins had to resolve a raid1 with a missing device the next time the system rebooted. So the reproducer was:
1. Device disappears.
2. Reboot occurs.
3. Filesystem fails to mount due to missing device.
Thus
4. Sysadmin mounts with "-o degraded" and btrfs writes profile=single chunks.
5. For whatever reasons sysadmin doesn't succeed in replacing the missing device and rebalancing both data and metadata.
6. System reboots a second time.
7. The btrfs volume is now permanently read-only.
I vaguely remember that profile=degraded chunks may have been introduced some time between 2022 and now. Does this mean state #7 no longer occurs, because profile=degraded chunks are written at state #4, and that a sysadmin can still add a new device and rebalance after the second reboot?
Finally, are raid1, raid10, and raid1c3 and raid1c4 all comparably mature at this point?
Regards,
Nicholas