[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <81ebfa7d-e294-409c-a3a6-5acb6daeb03f@kernel.org>
Date: Wed, 22 Jun 2022 21:19:46 +0800
From: Chao Yu <chao@...nel.org>
To: qixiaoyu1 <qxy65535@...il.com>
Cc: Jaegeuk Kim <jaegeuk@...nel.org>,
linux-f2fs-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, liuchao12@...omi.com,
qixiaoyu1 <qixiaoyu1@...omi.com>
Subject: Re: [PATCH v2] resize.f2fs: add option to manually specify new
overprovision
On 2022/6/20 16:48, qixiaoyu1 wrote:
> From: liuchao12 <liuchao12@...omi.com>
>
> 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,
> and fix to check free space before grow. 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): Failed to get valid F2FS checkpoint
> mount(2) system call failed: Structure needs cleaning.
>
> Signed-off-by: qixiaoyu1 <qixiaoyu1@...omi.com>
Reviewed-by: Chao Yu <chao@...nel.org>
Thanks,
Powered by blists - more mailing lists