From: sho@tnes.nec.co.jp
To: adilger@clusterfs.com
Cc: cmm@us.ibm.com, jitendra@linsyssoft.com,
ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
tytso@mit.edu, sct@redhat.com
Subject: Re: [UPDATE][12/24]ext3 enlarge blocksize
Date: Tue, 30 May 2006 21:24:34 +0900 [thread overview]
Message-ID: <20060530212434sho@rifu.tnes.nec.co.jp> (raw)
Hi Andreas,
On May 26, 2006, Andreas wrote:
> At least part of this patch can be included into the patch series that
> Mingming has posted to allow larger block sizes on architectures that
> support it. This doesn't need a separate COMPAT flag itself, since
> older kernels will already refuse to mount a filesystem with
> large blocks.
Do you mention block size? I don't use the COMPAT flag for large block
size, but for >2G blocks.
> On May 25, 2006 21:49 +0900, sho@tnes.nec.co.jp wrote:
> > @@ -1463,11 +1463,17 @@ static int ext3_fill_super (struct super
> > + if (blocksize > PAGE_SIZE) {
> > + printk(KERN_ERR "EXT3-fs: cannot mount filesystem with "
> > + "blocksize %u larger than PAGE_SIZE %u on %s\n",
> > + blocksize, PAGE_SIZE, sb->s_id);
> > + goto failed_mount;
> > + }
> > +
> > if (blocksize < EXT3_MIN_BLOCK_SIZE ||
> > - blocksize > EXT3_MAX_BLOCK_SIZE) {
> > + blocksize > EXT3_EXTENDED_MAX_BLOCK_SIZE) {
>
> We may as well just change EXT3_MAX_BLOCK_SIZE to be 65536,
> because no other
> code uses this value. It is already 65536 in the e2fsprogs.
Agree.
>
> > - printk(KERN_ERR
> > - "EXT3-fs: Unsupported filesystem
> blocksize %d on %s.\n",
> > - blocksize, sb->s_id);
> > + printk(KERN_ERR "EXT3-fs: Unsupported
> filesystem blocksize %d on %s.\n",
> > + blocksize, sb->s_id);
>
> I'm not sure why you changed the formatting of this message
> to now be longer
> than 80 columns.
Oops, you are right.
Thanks a lot, Andreas!
Cheers, sho
next reply other threads:[~2006-05-30 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 12:24 sho [this message]
2006-05-30 19:12 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2006-05-25 12:49 sho
2006-05-26 12:00 ` Andreas Dilger
2006-06-05 13:13 ` Johann Lombardi
2006-06-05 20:13 ` Andreas Dilger
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=20060530212434sho@rifu.tnes.nec.co.jp \
--to=sho@tnes.nec.co.jp \
--cc=adilger@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jitendra@linsyssoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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
all inboxes | Powered by JetHome®