From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] common/rc: support f2fs for _scratch_mkfs_sized
Date: Sat, 5 Dec 2015 21:11:31 +0800 [thread overview]
Message-ID: <5662E283.6090900@kernel.org> (raw)
In-Reply-To: <1449267345-79400-1-git-send-email-jaegeuk@kernel.org>
Hi Jaegeuk,
On 12/5/15 6:15 AM, Jaegeuk Kim wrote:
> The mkfs.f2fs has an option to build a certain sized filesystem by giving
> the number of sectors.
>
> So, this patch adds to use that.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> common/rc | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/common/rc b/common/rc
> index 4c2f42c..ef913b4 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -739,6 +739,10 @@ _scratch_mkfs_sized()
> $MKFS_REISER4_PROG $MKFS_OPTIONS -y -b $blocksize $SCRATCH_DEV \
> `expr $fssize / 1024`
> ;;
> + f2fs)
> + # mkfs.f2fs requires # of sectors as an input for the size
> + $MKFS_F2FS_PROG $MKFS_OPTIONS $SCRATCH_DEV `expr $fssize / 512`
In mkfs.f2fs, we will calculate fs size based on real sector size of block
device and the input sectors, so if sector size of block device is not 512, our
fs size calculated will be incorrect.
How about fixing it for supporting different sector size?
Thanks,
> + ;;
> *)
> _notrun "Filesystem $FSTYP not supported in _scratch_mkfs_sized"
> ;;
>
next prev parent reply other threads:[~2015-12-05 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 22:15 [PATCH 1/3] common/rc: support f2fs for _scratch_mkfs_sized Jaegeuk Kim
2015-12-04 22:15 ` [PATCH 2/3] common/config: add mkfs options for f2fs Jaegeuk Kim
2015-12-04 22:15 ` [PATCH 3/3] f2fs/001: introduce a testcaes for -ENOSPC with inline operation Jaegeuk Kim
2015-12-05 13:11 ` Chao Yu [this message]
2015-12-08 0:08 ` [f2fs-dev] [PATCH 1/3] common/rc: support f2fs for _scratch_mkfs_sized Jaegeuk Kim
2015-12-08 0:16 ` [PATCH 1/3 v2] " Jaegeuk Kim
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=5662E283.6090900@kernel.org \
--to=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).