On 10/21, Shinichiro Kawasaki wrote:
> On Oct 20, 2022 / 16:18, Jaegeuk Kim wrote:
>
> ...
>
> > Thanks, I think that fix looks good to me. I applied into the original
> > patch.
> > https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?h=dev&id=281d3e72370f6c39c0d57acaf
On Oct 20, 2022 / 16:18, Jaegeuk Kim wrote:
...
> Thanks, I think that fix looks good to me. I applied into the original patch.
> https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?h=dev&id=281d3e72370f6c39c0d57acaf37a7f0e003ddd28
Oh, happy to know that the fix is goo
On 10/20, Shinichiro Kawasaki wrote:
> On Oct 10, 2022 / 15:15, Jaegeuk Kim wrote:
> > As f2fs becomes more resilient for GCs, let's give the marginal
> > overprovision
> > space back to user.
> >
> > Signed-off-by: Jaegeuk Kim
>
> Hello Jaegeuk,
>
> Using the dev branch of f2fs-tools repo, I
On Oct 10, 2022 / 15:15, Jaegeuk Kim wrote:
> As f2fs becomes more resilient for GCs, let's give the marginal overprovision
> space back to user.
>
> Signed-off-by: Jaegeuk Kim
Hello Jaegeuk,
Using the dev branch of f2fs-tools repo, I observed mkfs.f2fs failure with zoned
block devices:
As f2fs becomes more resilient for GCs, let's give the marginal overprovision
space back to user.
Signed-off-by: Jaegeuk Kim
---
fsck/resize.c | 8
include/f2fs_fs.h | 6 --
mkfs/f2fs_format.c | 9 ++---
3 files changed, 14 insertions(+), 9 deletions(-)
diff --git a/fsck/
