Commit 972fbf77 authored Oct 18, 2008 by Josef Bacik Committed by Linus Torvalds Oct 20, 2008

ext3: don't try to resize if there are no reserved gdt blocks left



When trying to resize a ext3 fs and you run out of reserved gdt blocks,
you get an error that doesn't actually tell you what went wrong, it just
says that the gdb it picked is not correct, which is the case since you
don't have any reserved gdt blocks left.  This patch adds a check to make
sure you have reserved gdt blocks to use, and if not prints out a more
relevant error.

Signed-off-by: Josef Bacik <jbacik@redhat.com>
Cc: <linux-ext4@vger.kernel.org>
Cc: Andreas Dilger <adilger@sun.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

parent 885e353c

fs/ext3/resize.c

+2 −1

Original line number	Diff line number	Diff line
		@@ -790,7 +790,8 @@ int ext3_group_add(struct super_block sb, struct ext3_new_group_data input)

		if (reserved_gdb \|\| gdb_off == 0) {
		if (!EXT3_HAS_COMPAT_FEATURE(sb,
		EXT3_FEATURE_COMPAT_RESIZE_INODE)){
		EXT3_FEATURE_COMPAT_RESIZE_INODE)
		\|\| !le16_to_cpu(es->s_reserved_gdt_blocks)) {
		ext3_warning(sb, __func__,
		"No reserved GDT blocks, can't resize");
		return -EPERM;