When users set GC_URGENT or GC_MID, they expected to do GCs right away.
But, there's a condition to bypass it. Let's indicate we need to do now
in the thread.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/gc.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/gc.c b/fs
Let's try to flush dirty inode again to improve subtle i_blocks mismatch.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/node.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index 836c79a20afc..4181d03a7ef7 100644
--- a/fs/f2fs/node.c
+++ b/f
This fixes the below corruption.
[345393.335389] F2FS-fs (vdb): sanity_check_inode: inode (ino=6d0, mode=33206)
should not have inline_data, run fsck to fix
Cc:
Fixes: 677a82b44ebf ("f2fs: fix to do sanity check for inline inode")
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/namei.c | 16 ++
On 06/17, Chao Yu wrote:
> On 2022/6/17 0:22, Jaegeuk Kim wrote:
> > On 06/16, Chao Yu wrote:
> > > On 2022/6/16 0:54, Jaegeuk Kim wrote:
> > > > On 06/15, Chao Yu wrote:
> > > > > On 2022/6/11 2:32, Daeho Jeong wrote:
> > > > > > From: Daeho Jeong
> > > > > >
> > > > > > Made iostat related lock