From: Ashish Sangwan <ashishsangwan2@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>, adilger@dilger.ca
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Ashish Sangwan <a.sangwan@samsung.com>,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [PATCH]mke2fs: Calculate journal blocks just after fs initialize
Date: Wed, 5 Jun 2013 13:55:31 +0530 [thread overview]
Message-ID: <CAOiN93=QDRpp7bHygcnom0ZMwU-dc1dRaGf62qw3GDXgCb7uKQ@mail.gmail.com> (raw)
In-Reply-To: <1368243733-1600-1-git-send-email-ashish.sangwan2@gmail.com>
any comments?
On Sat, May 11, 2013 at 9:12 AM, Ashish Sangwan
<ashishsangwan2@gmail.com> wrote:
> From: Ashish Sangwan <a.sangwan@samsung.com>
>
> We can calculate journal blocks as soon as blocksize is set.
> It will help to figure out wrong journal blocks count earlier.
> This will save some un-necessary initialization.
>
> Without patch output =>
> mke2fs /dev/sdc1 -J size=1048576
> mke2fs 1.42.7 (21-Jan-2013)
> Filesystem label=
> OS type: Linux
> Block size=4096 (log=2)
> Fragment size=4096 (log=2)
> Stride=0 blocks, Stripe width=0 blocks
> 61312 inodes, 244936 blocks
> 12246 blocks (5.00%) reserved for the super user
> First data block=0
> Maximum filesystem blocks=251658240
> 8 block groups
> 32768 blocks per group, 32768 fragments per group
> 7664 inodes per group
> Superblock backups stored on blocks:
> 32768, 98304, 163840, 229376
>
> Allocating group tables: done
> Writing inode tables: done
>
> The requested journal size is 268435456 blocks; it must be
> between 1024 and 10240000 blocks. Aborting.
>
>
> With patch output =>
> mke2fs /dev/sdc1 -J size=1048576
> mke2fs 1.42.7 (21-Jan-2013)
>
> The requested journal size is 268435456 blocks; it must be
> between 1024 and 10240000 blocks. Aborting.
>
> Signed-off-by: Ashish Sangwan <a.sangwan@samsung.com>
> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
> ---
> misc/mke2fs.c | 8 ++++++--
> 1 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/misc/mke2fs.c b/misc/mke2fs.c
> index bbf477a..0232053 100644
> --- a/misc/mke2fs.c
> +++ b/misc/mke2fs.c
> @@ -2407,6 +2407,12 @@ int main (int argc, char *argv[])
> com_err(device_name, retval, _("while setting up superblock"));
> exit(1);
> }
> +
> + /* Calculate journal blocks */
> + if (!journal_device && ((journal_size) ||
> + (fs_param.s_feature_compat &
> + EXT3_FEATURE_COMPAT_HAS_JOURNAL)))
> + journal_blocks = figure_journal_size(journal_size, fs);
> fs->progress_ops = &ext2fs_numeric_progress_ops;
>
> /* Check the user's mkfs options for metadata checksumming */
> @@ -2683,8 +2689,6 @@ int main (int argc, char *argv[])
> } else if ((journal_size) ||
> (fs_param.s_feature_compat &
> EXT3_FEATURE_COMPAT_HAS_JOURNAL)) {
> - journal_blocks = figure_journal_size(journal_size, fs);
> -
> if (super_only) {
> printf(_("Skipping journal creation in super-only mode\n"));
> fs->super->s_journal_inum = EXT2_JOURNAL_INO;
> --
> 1.7.2.3
>
next prev parent reply other threads:[~2013-06-05 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 3:42 [PATCH]mke2fs: Calculate journal blocks just after fs initialize Ashish Sangwan
2013-06-05 8:25 ` Ashish Sangwan [this message]
2013-06-21 3:03 ` Theodore Ts'o
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='CAOiN93=QDRpp7bHygcnom0ZMwU-dc1dRaGf62qw3GDXgCb7uKQ@mail.gmail.com' \
--to=ashishsangwan2@gmail.com \
--cc=a.sangwan@samsung.com \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=tytso@mit.edu \
/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).