mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: sho@tnes.nec.co.jp
Cc: cmm@us.ibm.com, jitendra@linsyssoft.com,
	ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [UPDATE][12/24]ext3 enlarge blocksize
Date: Fri, 26 May 2006 06:00:32 -0600	[thread overview]
Message-ID: <20060526120032.GN5964@schatzie.adilger.int> (raw)
In-Reply-To: <20060525214902sho@rifu.tnes.nec.co.jp>

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.

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.

> -		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.

> diff -upNr -X linux-2.6.17-rc4/Documentation/dontdiff linux-2.6.17-rc4/include/linux/ext3_fs.h linux-2.6.17-rc4.tmp/include/linux/ext3_fs.h
> --- linux-2.6.17-rc4/include/linux/ext3_fs.h	2006-05-25 16:33:29.711659209 +0900
> +++ linux-2.6.17-rc4.tmp/include/linux/ext3_fs.h	2006-05-25 16:33:52.247791746 +0900
> @@ -86,6 +86,7 @@ struct statfs;
>   */
>  #define EXT3_MIN_BLOCK_SIZE		1024
>  #define	EXT3_MAX_BLOCK_SIZE		4096
> +#define        EXT3_EXTENDED_MAX_BLOCK_SIZE    65536
>  #define EXT3_MIN_BLOCK_LOG_SIZE		  10
>  #ifdef __KERNEL__
>  # define EXT3_BLOCK_SIZE(s)		((s)->s_blocksize)

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.


  reply	other threads:[~2006-05-26 12:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 12:49 sho
2006-05-26 12:00 ` Andreas Dilger [this message]
2006-06-05 13:13   ` Johann Lombardi
2006-06-05 20:13     ` Andreas Dilger
2006-05-30 12:24 sho
2006-05-30 19:12 ` 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=20060526120032.GN5964@schatzie.adilger.int \
    --to=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=sho@tnes.nec.co.jp \
    /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®