Re: [f2fs-dev] [RFC PATCH 2/8] fsck.f2fs: do not fix corrupted nat entries in build_nat_area_bitmap

2017-10-31 Thread Chao Yu
On 2017/10/31 16:57, Sheng Yong wrote: > Hi, Chao > > On 2017/10/31 15:20, Chao Yu wrote: >> On 2017/10/31 9:38, Sheng Yong wrote: >>> Fixing corrupted data depends on c.fix_on. If it's not set, we should not >>> force fixing corrupted data. So if nat entries are found invalid when >>> building

Re: [f2fs-dev] [RFC PATCH 2/8] fsck.f2fs: do not fix corrupted nat entries in build_nat_area_bitmap

2017-10-31 Thread Sheng Yong
Hi, Chao On 2017/10/31 15:20, Chao Yu wrote: On 2017/10/31 9:38, Sheng Yong wrote: Fixing corrupted data depends on c.fix_on. If it's not set, we should not force fixing corrupted data. So if nat entries are found invalid when building nat_area_bitmap, we should just set c.bug_on, and fix it

Re: [f2fs-dev] [RFC PATCH 2/8] fsck.f2fs: do not fix corrupted nat entries in build_nat_area_bitmap

2017-10-31 Thread Chao Yu
On 2017/10/31 9:38, Sheng Yong wrote: > Fixing corrupted data depends on c.fix_on. If it's not set, we should not > force fixing corrupted data. So if nat entries are found invalid when > building nat_area_bitmap, we should just set c.bug_on, and fix it later. It looks comments and code change

[f2fs-dev] [RFC PATCH 2/8] fsck.f2fs: do not fix corrupted nat entries in build_nat_area_bitmap

2017-10-30 Thread Sheng Yong
Fixing corrupted data depends on c.fix_on. If it's not set, we should not force fixing corrupted data. So if nat entries are found invalid when building nat_area_bitmap, we should just set c.bug_on, and fix it later. Signed-off-by: Sheng Yong --- fsck/mount.c | 21