raid1 recovery w bitmap + PAR2
Code:
recovery = 49.9% (724112960/1448225792) finish=1.0min speed=11321520K/sec And yes, mdadm is showing an effective recovery rate of 11.3GB/s thanks to the write-intent internal bitmap. The whole process of recovering the 1.4TB took about 100 seconds on 64bit 14.0, 3.2.45 kernel, RAID10f2. After many hours and much angst looking at ZoL/btrfs current buglists I could not pull the trigger on conversion and so stuck with ext4, added the bitmaps and went with PAR2 for bitrot protection.
Here's the quick script used to create checksums. Run a small test and see if it meets your needs, or even works. It has not been cleaned up. I used the parallel par2 http://slackbuilds.org/repository/14...r2cmdline-tbb/ which is why the rudimentary simultaneous job management. Cheers, [Update] Root cause was a marginal SATA cable, old logs show over a year of sporadic SATA resets. The above recovery was a simple hot-add of the same partition back in to the array. A subsequent scrub took 7.07 hours on an otherwise unused system, so the bitmap in this case effectively reduced rebuild by a factor of 250 (100 vs 25.5K seconds). Code:
#!/bin/bash |
Thanks for posting your update, off of the 0-reply list now.
//NTLB |
Quote:
After full recovery I went ahead w btrfs on one disk and duplicated files from ext4. After almost a year, 2 kernel and 1 btrfs-progs updates, there were zero failure/corruption or other incidents on either disk, however it was write performance that finally triggered replacing btrfs with ext4+PAR2: Streaming writes from ext4 -> btrfs averaged just under 49MB/s while ext4 -> ext4 averaged 111MB/s even during ext4 lazy initialization. Cheers, |
All times are GMT -5. The time now is 04:59 PM. |