From: Theodore Tso <tytso@MIT.EDU>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH][e2fsprogs] New bitmap and inode table allocation for FLEX_BG
Date: Thu, 3 Apr 2008 23:24:43 -0400 [thread overview]
Message-ID: <20080404032443.GA362@mit.edu> (raw)
In-Reply-To: <20080403092858.5e3a7bb2@gara.konoha.net>
On Thu, Apr 03, 2008 at 09:28:58AM -0500, Jose R. Santos wrote:
> I blame Undo Manager for being so slow that cause me to skip some of
> the testing needed to be done.
If that means we need a patch to disable the undo manager, via a
command-line option, feel free. :-)
> I was incorrectly checking the feature
> flag instead of checking the value of fs->super->s_log_groups_per_flex.
Actually, you should check both, and we need to make mke2fs have an
intelligent default, which can be overridden via mke2fs.conf.
Also, it looks like this patch doesn't create a valid filesystem in
combination with meta_bg:
mke2fs G 32 -O meta_bg,flex_bg,uninit_groups,^resize_inode /tmp/foo.img
Then try running "e2fsck -f /tmp/foo.img" with the patch applied.
One obvious question is why is this patch so fragile....? Is there
some way we can make it more likely not to break given other changes
to e2fsprogs in the future.
- Ted
next prev parent reply other threads:[~2008-04-04 3:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 3:13 [PATCH][e2fsprogs] New bitmap and inode table allocation for FLEX_BG Jose R. Santos
2008-04-03 13:12 ` Theodore Tso
2008-04-03 14:28 ` Jose R. Santos
2008-04-04 3:24 ` Theodore Tso [this message]
2008-04-04 5:37 ` Jose R. Santos
2008-04-04 12:43 ` Theodore Tso
2008-04-04 15:20 ` Jose R. Santos
2008-04-03 14:29 ` [PATCH][e2fsprogs] mke2fs: " Jose R. Santos
-- strict thread matches above, loose matches on Subject: below --
2008-02-07 17:09 [PATCH] e2fsprogs: " Jose R. Santos
2008-02-08 5:11 ` Andreas Dilger
2008-02-08 17:37 ` Jose R. Santos
2008-02-11 4:33 ` Theodore Tso
2008-02-11 15:05 ` Jose R. Santos
2008-01-11 17:28 Jose R. Santos
2008-01-11 21:01 ` Andreas Dilger
2008-01-11 22:11 ` Jose R. Santos
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=20080404032443.GA362@mit.edu \
--to=tytso@mit.edu \
--cc=jrs@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
/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.