On 2017/1/5 6:48, Jaegeuk Kim wrote:
> On 01/04, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>> On 2016/12/31 2:51, Jaegeuk Kim wrote:
>>> Otherwise we can remain wrong curseg->next_blkoff, resulting in fsck
>>> failure.
>>
>> Could you explain more about this case?
>
> I remember that I hit an fsck failure
On 01/04, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2016/12/31 2:51, Jaegeuk Kim wrote:
> > Otherwise we can remain wrong curseg->next_blkoff, resulting in fsck
> > failure.
>
> Could you explain more about this case?
I remember that I hit an fsck failure when I was testing f2fs with an smr drive.
I
Hi Jaegeuk,
On 2016/12/31 2:51, Jaegeuk Kim wrote:
> Otherwise we can remain wrong curseg->next_blkoff, resulting in fsck failure.
Could you explain more about this case?
Thanks,
>
> Signed-off-by: Jaegeuk Kim
> ---
> fs/f2fs/segment.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --gi
3 matches
Mail list logo