public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: e2fsprogs: Patches to resize2fs
Date: Tue, 17 Jun 2008 02:06:29 -0400	[thread overview]
Message-ID: <1213682792-4878-1-git-send-email-tytso@mit.edu> (raw)

The following patches fix resize2fs support for uninit_bg filesystems,
as well as a rather embarassing bug which I had introduced while
making mke2fs -j more efficient.  The final patch prohibits resizing
filesystems that have flex_bg enabled and do not have the resize_inode
feature enabled, since my testing has found a nasty bug in the flex_bg
&& !resize_inode case, and I fix isn't going to be coming right away.

In any case, this should make e2fsprogs work much better; at this
point resizing should be in good shape except for:

1)  flex_bg with on-line resizing

and

2)  flex_bg && !resize_inode with off-line resizing.

There may also be problems with flex_bg && uninit_bg; more testing is
needed there to be 100% sure there's nothing hiding in that particular
feature set combination.

						- Ted



             reply	other threads:[~2008-06-17  6:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17  6:06 Theodore Ts'o [this message]
2008-06-17  6:06 ` [PATCH] resize2fs: Fix support for the uninit_bg feature Theodore Ts'o
2008-06-17  6:06   ` [PATCH] ext2fs_zero_blocks: Avoid clearing more blocks than requested Theodore Ts'o
2008-06-17  6:06     ` [PATCH] resize2fs: Prohibit the combination of flex_bg and !resize_inode Theodore Ts'o
2008-06-17 15:16   ` [PATCH] resize2fs: Fix support for the uninit_bg feature Andreas Dilger
2008-06-17 16:30     ` Theodore Tso
2008-06-23 20:42       ` 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=1213682792-4878-1-git-send-email-tytso@mit.edu \
    --to=tytso@mit.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox