Did i get you right?
Please correct me if i am wrong:
Scrubbing seems to have been fixed, you only have to run it once.
Hotplugging (temporary connection loss) is affected by the write hole bug, and
will create undetectable errors every 16 TB (crc32 limitation).
The write Hole Bug can affect
Write hole:
> The data will be readable until one of the data blocks becomes
> inaccessible (bad sector or failed disk). This is because it is only the
> parity block that is corrupted (old data blocks are still not modified
> due to btrfs CoW), and the parity block is only required when
I guess that covers most topics, two last questions:
Will the write hole behave differently on Raid 6 compared to Raid 5 ?
Is there any benefit of running Raid 5 Metadata compared to Raid 1 ?
-
Running time of 55:06:35 indicates that the counter is right, it is not enough
time to scrub the entire array using hdd.
2TiB might be right if you only scrubbed one disc, "sudo btrfs scrub start
/dev/sdx1" only scrubs the selected partition,
whereas "sudo btrfs scrub start
Could you show scrub status -d, then start a new scrub (all drives) and show
scrub status -d again? This may help us diagnose the problem.
Am 15-Aug-2018 09:27:40 +0200 schrieb men...@gmail.com:
> I needed to resume scrub two times after an unclear shutdown (I was
> cooking and using too much
I am searching for more information regarding possible bugs related to BTRFS
Raid 5/6. All sites i could find are incomplete and information contradicts
itself:
The Wiki Raid 5/6 Page (https://btrfs.wiki.kernel.org/index.php/RAID56)
warns of the write hole bug, stating that your data remains
