linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@MIT.EDU>
Cc: linux-ext4@vger.kernel.org
Subject: Re: #blocks per group too big: 37265
Date: Thu, 03 Apr 2008 14:24:38 -0500	[thread overview]
Message-ID: <47F52EF6.5040905@redhat.com> (raw)
In-Reply-To: <20080403191254.GG13486@mit.edu>

Theodore Tso wrote:
> On Thu, Apr 03, 2008 at 12:58:30PM -0500, Eric Sandeen wrote:
>>> I obtained the 1.39-tyt3 version of e2fsprogs, and did:
> 
>>> | mke2fs 1.38 (30-Jun-2005)
> 
>> I'd probably not use 1.39-tyt3... that's pretty old.  (see the 2005?) :)
> 
> Actually, e2fsprogs 1.39-tyt isn't that old (April 2007).  The 2005 is
> because the mke2fs in use was 1.38, not 1.39.  (Which was probably
> another problem.)

Ah, missed that.

Ted, it looks like the stride value is still getting % 65536, just FWIW.

[e2fsprogs]$ misc/mke2fs -F -E stride=65536 testit
mke2fs 1.40.8 (13-Mar-2008)
Invalid stride parameter: 65536

Bad option(s) specified:
...

[e2fsprogs]$ misc/mke2fs -F -E stride=65537 testit
mke2fs 1.40.8 (13-Mar-2008)

Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
...

I'll send a patch for it in a bit, trying not to get too distracted
right now ;)

-Eric


  reply	other threads:[~2008-04-03 19:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 16:19 #blocks per group too big: 37265 Paul Slootman
2008-04-03 17:58 ` Eric Sandeen
2008-04-03 19:12   ` Theodore Tso
2008-04-03 19:24     ` Eric Sandeen [this message]
2008-04-03 18:39 ` Theodore Tso
     [not found] ` <20080403183929.GE13486@40mit.edu>
2008-04-04  9:21   ` Paul Slootman
2008-04-04 12:08     ` Theodore Tso
2008-04-04 12:56       ` Paul Slootman

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=47F52EF6.5040905@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --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).