On 2017-04-26 02:13, Qu Wenruo wrote:
>
>
> At 04/26/2017 01:58 AM, Goffredo Baroncelli wrote:
>> I Qu,
>>
>> I tested these two patches on top of 4.10.12; however when I
>> corrupt disk1, It seems that BTRFS is still unable to rebuild
>> parity.
>>
>> Because in the past the patches set V4 was
At 04/26/2017 01:58 AM, Goffredo Baroncelli wrote:
I Qu,
I tested these two patches on top of 4.10.12; however when I corrupt disk1, It
seems that BTRFS is still unable to rebuild parity.
Because in the past the patches set V4 was composed by 5 patches and this one
(V5) is composed by only
I Qu,
I tested these two patches on top of 4.10.12; however when I corrupt disk1, It
seems that BTRFS is still unable to rebuild parity.
Because in the past the patches set V4 was composed by 5 patches and this one
(V5) is composed by only 2 patches, are these 2 sufficient to solve all known
b
On Fri, Apr 14, 2017 at 08:35:55AM +0800, Qu Wenruo wrote:
> When scrubbing a RAID5 which has recoverable data corruption (only one
> data stripe is corrupted), sometimes scrub will report more csum errors
> than expected. Sometimes even unrecoverable error will be reported.
>
> The problem can be
When scrubbing a RAID5 which has recoverable data corruption (only one
data stripe is corrupted), sometimes scrub will report more csum errors
than expected. Sometimes even unrecoverable error will be reported.
The problem can be easily reproduced by the following steps:
1) Create a btrfs with RAI
