From: nl6720 via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net, Chao Yu <chao@kernel.org>
Subject: Re: [f2fs-dev] [PATCH] f2fs-tools: prefer physical over logical block size
Date: Tue, 29 Apr 2025 19:53:49 +0300 [thread overview]
Message-ID: <5173683.GXAFRqVoOG@nl6720.me> (raw)
In-Reply-To: <da5d8c00-4835-4635-a5f5-8610dd79a579@kernel.org>
On Monday, 28 April 2025 10:33:18 EEST Chao Yu wrote:
> How about printing block size of f2fs as below:
>
> output of mkfs.f2fs:
>
> Info: sector size = 512
> Info: total sectors = 16777216 (8192 MB)
> Info: block size = 4096
mkfs.f2fs printing it would be nice.
I'm still confused by the "sector size" in mkfs.f2fs output. Is it simply the
drive's logical sector size and not a fundamental part of the file system
like with xfs?
nl6720
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2025-04-29 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 1:36 [f2fs-dev] [PATCH] f2fs-tools: prefer physical over logical block size nl6720 via Linux-f2fs-devel
2025-04-27 8:45 ` Chao Yu via Linux-f2fs-devel
2025-04-27 9:30 ` nl6720 via Linux-f2fs-devel
2025-04-28 7:33 ` Chao Yu via Linux-f2fs-devel
2025-04-29 16:53 ` nl6720 via Linux-f2fs-devel [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=5173683.GXAFRqVoOG@nl6720.me \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=devnull@nl6720.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.