[f2fs-dev] [PATCH] f2fs: avoid frequent costly fsck triggers

2018-11-27 Thread Jaegeuk Kim
If we want to re-enable nat_bits, we rely on fsck which requires full scan of directory tree. Let's do that by regular fsck or unclean shutdown. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h

Re: [f2fs-dev] [PATCH] f2fs: avoid frequent costly fsck triggers

2018-11-27 Thread Chao Yu
Hi Jaeguek, On 2018/11/28 15:31, Jaegeuk Kim wrote: > If we want to re-enable nat_bits, we rely on fsck which requires full scan > of directory tree. Let's do that by regular fsck or unclean shutdown. Reviewed-by: Chao Yu BTW, I have patch made some month ago... In order to detect nat_bits

Re: [f2fs-dev] fsck: reset i_gc_failures from 0x1 to 0x00

2018-11-27 Thread Michael Laß
Hi, > Am 27.11.2018 um 01:08 schrieb Jaegeuk Kim : > On 11/26, Michael Laß wrote: >> >>> Am 26.11.2018 um 15:09 schrieb Chao Yu : >>> But the problem here is even .i_gc_failures's value is one which was >>> initialized >>> duing inode creation by old kernel, and it never be increased by GC

[f2fs-dev] [PATCH] fsck.f2fs: introduce preen mode 2

2018-11-27 Thread Chao Yu
As Michael reported: after updating to f2fs-tools 1.12.0, a routine fsck of my file systems took quite a while and output ten-thousands instances of the following line: > [FIX] (fsck_chk_inode_blk: 954) --> Regular: 0xXYZ reset i_gc_failures from > 0x1 to 0x00 The reason is that: We start to

Re: [f2fs-dev] [PATCH 3/7] fscrypt: Remove filesystem specific build config option

2018-11-27 Thread Chandan Rajendra
On Tuesday, November 27, 2018 5:44:24 AM IST Eric Biggers wrote: > Hi Chandan, > > On Mon, Nov 19, 2018 at 10:53:20AM +0530, Chandan Rajendra wrote: > > In order to have a common code base for fscrypt "post read" processing > > for all filesystems which support encryption, this commit removes > >

Re: [f2fs-dev] [PATCH 7/7] fsverity: Remove filesystem specific build config option

2018-11-27 Thread Chandan Rajendra
On Tuesday, November 27, 2018 6:15:30 AM IST Eric Biggers wrote: > Hi Chandan, > > On Mon, Nov 19, 2018 at 10:53:24AM +0530, Chandan Rajendra wrote: > > In order to have a common code base for fsverity "post read" processing > > for all filesystems which support per-file verity, this commit

Re: [f2fs-dev] [PATCH 4/7] Add S_VERITY and IS_VERITY()

2018-11-27 Thread Chandan Rajendra
On Tuesday, November 27, 2018 5:38:38 AM IST Eric Biggers wrote: > Hi Chandan, > > On Mon, Nov 19, 2018 at 10:53:21AM +0530, Chandan Rajendra wrote: > > Similar to S_ENCRYPTED/IS_ENCRYPTED(), this commit adds > > S_VERITY/IS_VERITY() to be able to check if a VFS inode has verity > > information