Hi,
I'm currently trying out f2fs safe resize / shrink on Android.
(Size: 98 GiB used out of 221 GiB, 501,313 nodes, resize to 180 GiB)
It seems to work surprisingly well, the only improvement that can be
made seems to be updating quota.
After resize, fsck complains:
[ERROR]
Otherwise, in image which doesn't support compression feature,
page_array_entry will be initialized w/o use.
Signed-off-by: Chao Yu
---
fs/f2fs/compress.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
index 24824cd96f36..fa237e5c7173 100644
---
On 2022/6/18 6:31, Jaegeuk Kim wrote:
Let's try to flush dirty inode again to improve subtle i_blocks mismatch.
Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
On 2022/6/18 6:31, Jaegeuk Kim wrote:
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.
.should_migrate_blocks is used to force migrating blocks in full
section, so what is the
On 2022/6/18 6:31, Jaegeuk Kim wrote:
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
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 locks safe to be called from irq context again.
Will be better to add a 'Fixes' line?
Added some tags. Thanks,
On 2022/6/16 0:56, Jaegeuk Kim wrote:
Signed-off-by: Jaegeuk Kim
---
tools/f2fs_io/f2fs_io.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tools/f2fs_io/f2fs_io.c b/tools/f2fs_io/f2fs_io.c
index 2f0fc7b25d41..e7359836b126 100644
--- a/tools/f2fs_io/f2fs_io.c
+++
On 2022/6/14 19:49, qixiaoyu1 wrote:
Otherwise, after grow, kernel may report below error message
when we mount the image if -o parameter is specified during resize:
F2FS-fs (loop0): invalid crc_offset: 0
F2FS-fs (loop0): Wrong valid_user_blocks: 16404, user_block_count: 13312
F2FS-fs (loop0):
On 2022/6/14 19:49, qixiaoyu1 wrote:
From: liuchao12
Make.f2fs supports manually specifying overprovision, and we expect
resize.f2fs to support it as well.
This change add a new '-o' option to manually specify overprovision.
Signed-off-by: liuchao12
---
fsck/main.c | 8 ++--
On 2022/6/15 7:17, Bart Van Assche wrote:
Change the type of the third argument of f2fs_report_zone() from void *
into struct blk_zone * to enable type checking.
Signed-off-by: Bart Van Assche
Reviewed-by: Chao Yu
Thanks,
___
Linux-f2fs-devel
On 2022/6/15 7:17, Bart Van Assche wrote:
Fix the f2fs-tools build on systems for which PAGE_SIZE != 4096.
Cc: Peter Collingbourne
Reported-by: Peter Collingbourne
Signed-off-by: Bart Van Assche
Reviewed-by: Chao Yu
Thanks,
___
On 2022/6/15 7:17, Bart Van Assche wrote:
The definition of struct blk_zone_report is as follows:
struct blk_zone_report {
__u64 sector;
__u32 nr_zones;
__u32 flags;
struct blk_zone zones[0];
Otherwise, we can get a wrong cp_error mark.
Cc:
Fixes: a7b8618aa2f0 ("f2fs: avoid infinite loop to flush node pages")
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/node.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index
13 matches
Mail list logo
