Launchpad has imported 3 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=132707.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2004-09-16T04:07:04+00:00 Alexandre wrote: >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: 1.umount /boot 2.dd if=/dev/holding/boot of=/tmp/boot.img 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>? [...] Reply at: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/26857/comments/0 ------------------------------------------------------------------------ On 2004-09-16T16:01:41+00:00 Thomas wrote: Fixed in rawhide in rpm e2fsprogs-1.35-10 or newer. Reply at: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/26857/comments/1 ------------------------------------------------------------------------ On 2004-10-02T20:09:39+00:00 Alexandre wrote: Confirmed fixed, thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/26857/comments/2 ** Changed in: e2fsprogs (Fedora) Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/26857 Title: glibc error during resize2fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/26857/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
