From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Gecko/20040809
Description of problem:
Taking a 98176-blocks long ext3 filesystem formatted to hold the /boot
device of an FC3-re0915.1 install, after a clean fsck, and attempting
to resize it to 50M, causes glibc to print a double-free error message
and abort the resize. The filesystem may be corrupted after this, but
fsck can easily fix it. No file corruption was detected. Growing the
filesystem to the original size produces the same problem.
I've experienced this with the old /boot filesystem of an FC2 install
as well, so I don't think it's extremely sensitive to filesystem
contents. I haven't had the guts to try it on bigger filesystems.
Version-Release number of selected component (if applicable):
e2fsprogs-1.35-9.5 glibc-2.3.3-53
Actual Results: resize2fs 1.35 (28-Feb-2004)
Resizing the filesystem on /tmp/boot.img to 51200 (1k) blocks.
*** glibc detected *** double free or corruption: 0x08218d68 ***
Aborted
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Gecko/20040809
Description of problem:
Taking a 98176-blocks long ext3 filesystem formatted to hold the /boot
device of an FC3-re0915.1 install, after a clean fsck, and attempting
to resize it to 50M, causes glibc to print a double-free error message
and abort the resize. The filesystem may be corrupted after this, but
fsck can easily fix it. No file corruption was detected. Growing the
filesystem to the original size produces the same problem.
I've experienced this with the old /boot filesystem of an FC2 install
as well, so I don't think it's extremely sensitive to filesystem
contents. I haven't had the guts to try it on bigger filesystems.
Version-Release number of selected component (if applicable):
e2fsprogs-1.35-9.5 glibc-2.3.3-53
How reproducible:
Always
Steps to Reproduce: holding/ boot of=/tmp/boot.img
1.umount /boot
2.dd if=/dev/
3.mount /boot
4.e2fsck -f /tmp/boot.img
5.resize2fs /tmp/boot.img 50M
Actual Results: resize2fs 1.35 (28-Feb-2004)
Resizing the filesystem on /tmp/boot.img to 51200 (1k) blocks.
*** glibc detected *** double free or corruption: 0x08218d68 ***
Aborted
Expected Results: It used to work
Additional info:
After resize2fs crashes, here's what I get:
# e2fsck -f /tmp/boot.img
e2fsck 1.35 (28-Feb-2004)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(6294--6549) -(6744--6999)
Fix<y>? yes
Free blocks count wrong for group #0 (431, counted=943).
Fix<y>? yes
Free blocks count wrong (40637, counted=41149).
Fix<y>? yes
/tmp/boot.img: ***** FILE SYSTEM WAS MODIFIED *****
/tmp/boot.img: 36/14336 files (5.6% non-contiguous), 10051/51200 blocks
[root@fri ~]# resize2fs /tmp/boot.img
resize2fs 1.35 (28-Feb-2004)
Resizing the filesystem on /tmp/boot.img to 98176 (1k) blocks.
*** glibc detected *** double free or corruption: 0x094c3d68 ***
Aborted
[root@fri ~]# e2fsck -f /tmp/boot.img
e2fsck 1.35 (28-Feb-2004)
Pass 1: Checking inodes, blocks, and sizes
Group 7's inode table at 57349 conflicts with some other fs block.
Relocate<y>? yes
Group 7's inode table at 57350 conflicts with some other fs block.
Relocate<y>? yes
Group 7's inode table at 57351 conflicts with some other fs block.
Relocate<y>?
[...]