On 2018/2/13 2:03, Jaegeuk Kim wrote:
> On 02/12, guoweichao wrote:
>>
>>
>> On 2018/2/12 11:40, Jaegeuk Kim wrote:
>>> On 02/12, guoweichao wrote:
On 2018/2/12 10:32, Jaegeuk Kim wrote:
> On 02/12, guoweichao wrote:
>> Hi Jaegeuk,
>>
>> On 2018/2/12 7:32, Jaegeuk
On 02/12, guoweichao wrote:
>
>
> On 2018/2/12 11:40, Jaegeuk Kim wrote:
> > On 02/12, guoweichao wrote:
> >>
> >>
> >> On 2018/2/12 10:32, Jaegeuk Kim wrote:
> >>> On 02/12, guoweichao wrote:
> Hi Jaegeuk,
>
> On 2018/2/12 7:32, Jaegeuk Kim wrote:
> > On 02/06, Weichao Guo
On 2018/2/12 11:40, Jaegeuk Kim wrote:
> On 02/12, guoweichao wrote:
>>
>>
>> On 2018/2/12 10:32, Jaegeuk Kim wrote:
>>> On 02/12, guoweichao wrote:
Hi Jaegeuk,
On 2018/2/12 7:32, Jaegeuk Kim wrote:
> On 02/06, Weichao Guo wrote:
>> There is a potential inconsistent
On 02/12, guoweichao wrote:
>
>
> On 2018/2/12 10:32, Jaegeuk Kim wrote:
> > On 02/12, guoweichao wrote:
> >> Hi Jaegeuk,
> >>
> >> On 2018/2/12 7:32, Jaegeuk Kim wrote:
> >>> On 02/06, Weichao Guo wrote:
> There is a potential inconsistent metadata case due to a cp block
> crc invalid
On 2018/2/12 10:32, Jaegeuk Kim wrote:
> On 02/12, guoweichao wrote:
>> Hi Jaegeuk,
>>
>> On 2018/2/12 7:32, Jaegeuk Kim wrote:
>>> On 02/06, Weichao Guo wrote:
There is a potential inconsistent metadata case due to a cp block
crc invalid in the latest checkpoint caused by hardware
On 02/12, guoweichao wrote:
> Hi Jaegeuk,
>
> On 2018/2/12 7:32, Jaegeuk Kim wrote:
> > On 02/06, Weichao Guo wrote:
> >> There is a potential inconsistent metadata case due to a cp block
> >> crc invalid in the latest checkpoint caused by hardware issues:
> >> 1) write nodes into segment x;
> >>
Hi Jaegeuk,
On 2018/2/12 7:32, Jaegeuk Kim wrote:
> On 02/06, Weichao Guo wrote:
>> There is a potential inconsistent metadata case due to a cp block
>> crc invalid in the latest checkpoint caused by hardware issues:
>> 1) write nodes into segment x;
>> 2) write checkpoint A;
>> 3) remove nodes
On 02/06, Weichao Guo wrote:
> There is a potential inconsistent metadata case due to a cp block
> crc invalid in the latest checkpoint caused by hardware issues:
> 1) write nodes into segment x;
> 2) write checkpoint A;
> 3) remove nodes in segment x;
> 4) write checkpoint B;
> 5) issue discard
There is a potential inconsistent metadata case due to a cp block
crc invalid in the latest checkpoint caused by hardware issues:
1) write nodes into segment x;
2) write checkpoint A;
3) remove nodes in segment x;
4) write checkpoint B;
5) issue discard or write datas into segment x;
6) sudden
