resize2fs: allow resizing flex_bg && !resize_inode file systems

With the bug fixes from the last two commits, resize2fs can now fully
support off-line resizing of file systems with flex_bg even if the
resize_inode feature is not present; so we no longer need to disallow
this combination.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
debian-1.42.9
Theodore Ts'o 2012-12-29 03:38:34 -05:00
parent ddcf1dbff2
commit 42519becda
1 changed files with 0 additions and 22 deletions

View File

@ -438,28 +438,6 @@ int main (int argc, char ** argv)
device_name);
exit(1);
}
/*
* XXXX The combination of flex_bg and !resize_inode
* causes major problems for resize2fs, since when the
* group descriptors grow in size this can potentially
* require multiple inode tables to be moved aside to
* make room, and resize2fs chokes rather badly in
* this scenario. It's a rare combination, except
* when a filesystem is expanded more than a certain
* size, so for now, we'll just prohibit that
* combination. This is something we should fix
* eventually, though.
*/
if ((fs->super->s_feature_incompat &
EXT4_FEATURE_INCOMPAT_FLEX_BG) &&
!(fs->super->s_feature_compat &
EXT2_FEATURE_COMPAT_RESIZE_INODE)) {
com_err(program_name, 0, _("%s: The combination of "
"flex_bg and\n\t!resize_inode features "
"is not supported by resize2fs.\n"),
device_name);
exit(1);
}
printf(_("Resizing the filesystem on "
"%s to %llu (%dk) blocks.\n"),
device_name, new_size, fs->blocksize / 1024);