From: Chao Yu <chao@kernel.org>
To: Sheng Yong <shengyong@oppo.com>, jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: avoid resetting non empty zone
Date: Wed, 29 May 2024 19:27:59 +0800 [thread overview]
Message-ID: <674665d7-33b5-4c33-afd8-637222ebf04c@kernel.org> (raw)
In-Reply-To: <20240529112411.380453-1-shengyong@oppo.com>
On 2024/5/29 19:24, Sheng Yong wrote:
> If curseg is not the first segment in its zone, the zone is not empty,
> and it should not be reset. This issue could be reproduced by:
>
> modprobe null_blk nr_devices=1 zoned=1 zone_max_open=6 zone_max_active=6 zone_size=1024 gb=30
> # /dev/vda is 4G
> mkfs.f2fs -m -c /dev/nullb0 /dev/vda -f
>
> while :; do
> mount /dev/vda /mnt/
> dd if=/dev/zero of=/mnt/file bs=4K count=11 conv=fsync status=none
> if [ $? -ne 0 ]; then
> umount /mnt
> break
> fi
> f2fs_io shutdown 1 /mnt/file
> umount /mnt
> done
>
> And the error looks like:
> [ 123.169852] I/O error, dev nullb0, sector 41951232 op 0x1:(WRITE) flags 0x800 phys_seg 10 prio class 0
> [ 123.173070] F2FS-fs (vda): do_checkpoint failed err:-5, stop checkpoint
> dd: error writing '/mnt/testfile': Input/output error
>
> Signed-off-by: Sheng Yong <shengyong@oppo.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-05-29 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 11:24 [f2fs-dev] [PATCH] f2fs: avoid resetting non empty zone Sheng Yong via Linux-f2fs-devel
2024-05-29 11:27 ` Chao Yu [this message]
2024-05-30 10:01 ` [f2fs-dev] [PATCH v2] f2fs: alloc new section if curseg is not the first seg in its zone Sheng Yong via Linux-f2fs-devel
2024-06-12 15:55 ` patchwork-bot+f2fs
2024-06-12 15:55 ` [f2fs-dev] [PATCH] f2fs: avoid resetting non empty zone patchwork-bot+f2fs
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=674665d7-33b5-4c33-afd8-637222ebf04c@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shengyong@oppo.com \
/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;
as well as URLs for NNTP newsgroup(s).