From: Paul Slootman <paul@wurtel.net>
Subject: Re: #blocks per group too big: 37265
Date: Fri, 4 Apr 2008 14:56:29 +0200
Message-ID: <20080404125629.GA28519@msgid.wurtel.net>
References: <20080403161904.GA31670@msgid.wurtel.net> <20080404092120.GA28403@msgid.wurtel.net> <20080404120808.GA29297@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: linux-ext4@vger.kernel.org
Content-Disposition: inline
In-Reply-To: <20080404120808.GA29297@mit.edu>
Sender: linux-ext4-owner@vger.kernel.org

On Fri 04 Apr 2008, Theodore Tso wrote:
> On Fri, Apr 04, 2008 at 11:21:20AM +0200, Paul Slootman wrote:
> > I still end up with a "blocks per group" of 37265, and when mounted I'm
> > greeted with the message "EXT4-fs: #blocks per group too big: 37265".
> > Is the ext4 code in the 2.6.25-rc8 kernel too old? According to the
> > source the number of block per group must be <= 8 * blocksize; with 4k
> > blocks that would mean 32768, not 37265.
> > 
> > Even passing the -g option to explicitly set the blocks per group gets
> > ignored.
> 
> I didn't notice it initially, but it looks like you're using a 1.38
> mke2fs program and 1.39-tyt3 libraries.  I'm guessing that was

I downloaded e2fsprogs-64bit-x86_64.tar.bz2 from somewhere
(unfortunately I can't recall from where, but it was some link from a
page about ext4) and used the mkfs.ext3 from there, which ldd tells me
is statically linked. Apparently that version is too old.

> I was referring to e2fsprogs.  The latest version is available in the
> git repository, at:
> 
>     git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
>     http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=summary

Thanks for your help, I'll get that version and try again :-)

> that's where to find it.  (Please think very carefully before doing
> anything with production data, though!  We try to be very careful, but
> it's your data on the line at the end of the day.  :-)

This is on a system that provides 2nd stage backup (long term storage).
As I've just replaced the old 400G disks with 1TB disks, all the old
data is gone anyway, so any crashes or whatever won't immediataly lead
to problems :-)


Paul Slootman