On 07/13/2018 01:39 PM, Qu Wenruo wrote:
On 2018年07月13日 13:32, Anand Jain wrote:
But if you are planning to
record and start at transaction [14] then its an overkill because
transaction [19 and [20] are already in the disk.
Yes, I'm doing it overkilled.
Ah. Ok.
But it's already much better than scrub all block groups (my original
plan).
That's true. Which can be optimized later, but how? and scrub can't
fix RAID1.
How could scrub not fix RAID1?
Because degraded RAID1 allocates and writes data to the single chunks.
There is no mirrored copy of these data and it would remain as it is
even after the scrub.
For metadata or data with csum, just goes normal scrub.
Still need to fix the generation check for bg/parent transit
verification across the trees/disks part. IMO.
For data without csum, we know which device is resilvering, just use the
other copy.
If its a short term fix then its ok. But I think the approach is
similar to Liubo's InSync patch. Problem with this is, we will fail
to recover any data when the good disk throws media errors.
Thanks, Anand
Thanks,
Qu
Thanks, Anand
Thanks,
Qu
Thanks, Anand
Thanks,
Qu
[3] https://patchwork.kernel.org/patch/10403311/
Further, as we do a self adapting chunk allocation in RAID1, it
needs
balance-convert to fix. IMO at some point we have to provide
degraded
raid1 chunk allocation and also modify the scrub to be chunk
granular.
Thanks, Anand
Any idea on this?
Thanks,
Qu
Unlock: btrfs_fs_info::chunk_mutex
Unlock: btrfs_fs_devices::device_list_mutex
-----------------------------------------------------------------------
Thanks, Anand
--
To unsubscribe from this list: send the line "unsubscribe
linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe
linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe
linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
