The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid running out of free segments
Date: Wed, 12 Mar 2025 15:20:33 +0000	[thread overview]
Message-ID: <174179283306.831874.2260893071160537539.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250312090125.4014447-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Wed, 12 Mar 2025 17:01:25 +0800 you wrote:
> If checkpoint is disabled, GC can not reclaim any segments, we need
> to detect such condition and bail out from fallocate() of a pinfile,
> rather than letting allocator running out of free segment, which may
> cause f2fs to be shutdown.
> 
> reproducer:
> mkfs.f2fs -f /dev/vda 16777216
> mount -o checkpoint=disable:10% /dev/vda /mnt/f2fs
> for ((i=0;i<4096;i++)) do { dd if=/dev/zero of=/mnt/f2fs/$i bs=1M count=1; } done
> sync
> for ((i=0;i<4096;i+=2)) do { rm /mnt/f2fs/$i; } done
> sync
> touch /mnt/f2fs/pinfile
> f2fs_io pinfile set /mnt/f2fs/pinfile
> f2fs_io fallocate 0 0 4201644032 /mnt/f2fs/pinfile
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: fix to avoid running out of free segments
    https://git.kernel.org/jaegeuk/f2fs/c/f7f8932ca6bb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-03-12 15:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12  9:01 [PATCH] f2fs: fix to avoid running out of free segments Chao Yu
2025-03-12 15:20 ` patchwork-bot+f2fs [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=174179283306.831874.2260893071160537539.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox