From: Eric Sandeen <sandeen@redhat.com>
To: Robin Dong <hao.bigrat@gmail.com>
Cc: linux-ext4@vger.kernel.org, Robin Dong <sanbai@taobao.com>
Subject: Re: [PATCH] ext2: fix error msg when mounting fs with too-large blocksize
Date: Mon, 25 Apr 2011 10:11:26 -0500 [thread overview]
Message-ID: <4DB58F1E.3090303@redhat.com> (raw)
In-Reply-To: <1303626991-6704-1-git-send-email-hao.bigrat@gmail.com>
On 4/24/11 1:36 AM, Robin Dong wrote:
> From: Robin Dong <sanbai@taobao.com>
>
> When ext2 mounts a filesystem, it attempts to set the block device
> blocksize with a call to sb_set_blocksize, which can fail for
> several reasons. The current failure message in ext2 prints:
>
> EXT2-fs (loop1): error: blocksize is too small
>
> which is not correct in all cases. This can be demonstrated
> by creating a filesystem with
>
> # mkfs.ext2 -b 8192
>
> on a 4k page system, and attempting to mount it.
>
> Change the error message to a more generic:
>
> EXT2-fs (loop1): bad blocksize 8192
>
> to match the error message in ext3.
I couldn't have said it better myself :) As long as you're ok with not having the extra error message you originally had, for now ...
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
> Signed-off-by: Robin Dong <sanbai@taobao.com>
> ---
> fs/ext2/super.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ext2/super.c b/fs/ext2/super.c
> index 0a78dae..1dd62ed 100644
> --- a/fs/ext2/super.c
> +++ b/fs/ext2/super.c
> @@ -898,7 +898,8 @@ static int ext2_fill_super(struct super_block *sb, void *data, int silent)
> brelse(bh);
>
> if (!sb_set_blocksize(sb, blocksize)) {
> - ext2_msg(sb, KERN_ERR, "error: blocksize is too small");
> + ext2_msg(sb, KERN_ERR,
> + "error: bad blocksize %d", blocksize);
> goto failed_sbi;
> }
>
next prev parent reply other threads:[~2011-04-25 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 6:36 [PATCH] ext2: fix error msg when mounting fs with too-large blocksize Robin Dong
2011-04-24 7:17 ` Coly Li
2011-04-25 15:11 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-05 2:44 Robin Dong
2011-05-05 11:23 ` Jan Kara
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=4DB58F1E.3090303@redhat.com \
--to=sandeen@redhat.com \
--cc=hao.bigrat@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sanbai@taobao.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).