Bug 443541

Description of problem:
Can't perform online resize of ext3 filesystem using resize2fs with a block size
of 1024 bytes.  The following error is reported:
resize2fs: Invalid argument While trying to add group #15625
Instead I have to unmount the filesystem and perform offline resize for it to
complete successfully.

Version-Release number of selected component (if applicable):
RHEL5.1
resize2fs 1.39 (29-May-2006)

How reproducible:
Everytime.  Customer had a 100G filesystem they wished to expand to 150G and the
error occured.  I have been able to reproduce using sparse loopback files.

Steps to Reproduce:
dd if=/dev/zero of=disk1 seek=1024 count=1 bs=100M
losetup /dev/loop1 disk1 
pvcreate /dev/loop1
vgcreate loopvg1 /dev/loop1
lvcreate -l 100%VG loopvg1 -n looplv1
mkfs.ext3 -J size=64 -b 1024 /dev/loopvg1/looplv1 
mount /dev/loopvg1/looplv1 /mnt/loop
dd if=/dev/zero of=disk2 seek=1024 count=1 bs=50M
losetup /dev/loop2 disk2
pvcreate /dev/loop2
vgextend loopvg1 /dev/loop2
lvextend -l 100%VG /dev/loopvg1/looplv1 
resize2fs /dev/loopvg1/looplv1 
... error!

Actual results:
[root@dhcp-109 testing]# resize2fs /dev/loopvg1/looplv1 
resize2fs 1.39 (29-May-2006)
Filesystem at /dev/loopvg1/looplv1 is mounted on /mnt/loop; on-line resizing
required
Performing an on-line resize of /dev/loopvg1/looplv1 to 157433856 (1k) blocks.
resize2fs: Invalid argument While trying to add group #15625

Additional info:
Might be related to (or fixed with the patch in)
https://bugzilla.redhat.com/show_bug.cgi?id=425955 but the error is slightly
different and the journal is not as small (although the same block size was
being used).

[root@dhcp-109 testing]# dumpe2fs -h /dev/loopvg1/looplv1 
dumpe2fs 1.39 (29-May-2006)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          a0f4ef33-6885-40e9-9709-f6d9fbe06c57
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype
needs_recovery sparse_super
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              16000000
Block count:              128000001
Reserved block count:     6398312
Free blocks:              103212033
Free inodes:              13119477
First block:              1
Block size:               1024
Fragment size:            1024
Reserved GDT blocks:      168
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         1024
Inode blocks per group:   128
Filesystem created:       Tue Apr 22 13:35:30 2008
Last mount time:          Tue Apr 22 13:42:15 2008
Last write time:          Tue Apr 22 13:42:15 2008
Mount count:              1
Maximum mount count:      21
Last checked:             Tue Apr 22 13:35:30 2008
Check interval:           15552000 (6 months)
Next check after:         Sun Oct 19 13:35:30 2008
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      5927e30d-5927-4614-92b4-f96bb5760089
Journal backup:           inode blocks
Journal size:             64M

Problem also occurs for 32M journal (which is the default size if you don't
specify the '-J size=64' switch with mkfs.ext3).  Haven't tried any other size
journal.