All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH e2fsprogs] properly calculate overhead in ext2fs_initialize()
Date: Mon, 23 Jul 2007 13:00:15 -0500	[thread overview]
Message-ID: <46A4ECAF.3040800@redhat.com> (raw)
In-Reply-To: <20070722193129.GB16658@thunk.org>

Theodore Tso wrote:
> On Fri, Jul 20, 2007 at 04:47:14PM -0500, Eric Sandeen wrote:
>> For some odd geometries*, mkfs will try to allocate inode tables off
>> the end of the block group and fail, rather than warning that too
>> many inodes have been requested.
>>
>> This is because when ext2fs_initialize calculates metadata overhead,
>> it is only adding in group descriptor blocks and the superblock
>> if the *last* bg contains them - but the first bg also has all of 
>> the various metadata bits taking up space.
>>
>> Unconditionally adding those counts into the overhead seems to fix
>> it properly.
> 
> Yes, but it screws up the test right after that.  We need to calculate
> the overheads for both the first and last block group.  When I respun
> your patch and applied it to git, I fixed this.

Yep, I missed that.  Thanks for catching....

> I also added an explicit "Addresses-Red-Hat-Bugzilla: " entry to the
> commit log.  (This is mainly for your convenience when you're
> cherry-picking patches.)

Thanks, I appreciate that.

> Finally, your patch didn't apply because you apparently nuked a
> newline in the patch here:

Urhg, sorry.  Not sure how that happened.

Thanks,

-Eric

      reply	other threads:[~2007-07-23 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 21:47 [PATCH e2fsprogs] properly calculate overhead in ext2fs_initialize() Eric Sandeen
2007-07-22 19:31 ` Theodore Tso
2007-07-23 18:00   ` Eric Sandeen [this message]

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=46A4ECAF.3040800@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.