| View previous topic :: View next topic |
| Author |
Message |
iTux
Guru
Joined: 07 Sep 2004
Posts: 586
Location: Toronto
|
 Posted: Sun Oct 24, 2004 8:51 pm Post subject: resize2fs and memory corruption |
 |
|
Hi,
I tried to resize a ext2 fs on a LVM partition and I got:
| Code: |
curly david # resize2fs -p /dev/vg/daplus
resize2fs 1.35 (28-Feb-2004)
Resizing the filesystem on /dev/vg/daplus to 944128 (4k) blocks.
Begin pass 1 (max = 1)
Extending the inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
*** glibc detected *** double free or corruption: 0x080526d8 ***
Aborted
curly david #
curly david # resize2fs -p /dev/vg/daplus
resize2fs 1.35 (28-Feb-2004)
The filesystem is already 944128 blocks long. Nothing to do!
|
Question 1: What can I do about the error? I resize several partitions without any problems before. Maybe an upgrade of glibc was done.
Question 2: Rerunning resize2fs seems to say: already resized. And I also did a fsck and no errors report. Do you think the partition is ok and I should mount it without worry? Do you think that the fs was resized but maybe not "optimally", that is, data structures (ex: adding new inodes) not re-organized.
I tried shrinking it and regrowing it and still getting mem corruption.
I'm currently not on that computer right now. But I am running on ~x86.
Thanks,
iTux |
|
| Back to top |
|
 |
htj
n00b
Joined: 30 Apr 2002
Posts: 33
Location: Aalborg, Denmark
|
| Posted: Thu Dec 09, 2004 3:32 pm Post subject: Re: resize2fs and memory corruption |
|
|
| iTux wrote: | Hi,
I tried to resize a ext2 fs on a LVM partition and I got:
| Code: |
curly david # resize2fs -p /dev/vg/daplus
resize2fs 1.35 (28-Feb-2004)
Resizing the filesystem on /dev/vg/daplus to 944128 (4k) blocks.
Begin pass 1 (max = 1)
Extending the inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
*** glibc detected *** double free or corruption: 0x080526d8 ***
Aborted
curly david #
curly david # resize2fs -p /dev/vg/daplus
resize2fs 1.35 (28-Feb-2004)
The filesystem is already 944128 blocks long. Nothing to do!
|
Question 1: What can I do about the error? I resize several partitions without any problems before. Maybe an upgrade of glibc was done.
Question 2: Rerunning resize2fs seems to say: already resized. And I also did a fsck and no errors report. Do you think the partition is ok and I should mount it without worry? Do you think that the fs was resized but maybe not "optimally", that is, data structures (ex: adding new inodes) not re-organized.
I tried shrinking it and regrowing it and still getting mem corruption.
I'm currently not on that computer right now. But I am running on ~x86.
Thanks,
iTux |
Hi
I had the same problem some time ago. If fsck says you are ok, it is usually right, so you are in luck. I was not so lucky and fsck reported errors on the file system. I ended up copying the whole thing to another computer and recreate the file-system. There is some more information about the problem here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132707
Apparently the problem should be fixed, but I dont remember that lvm user-land utils have been upgraded, so be carefull.
Edit: The bug is of course in e2fsprogs, not in the lvm user utils. However e2fsprogs has not been updated since I did the faulty resize, so you should still be carefull :-/ |
|
| Back to top |
|
|
moja
n00b
Joined: 04 Feb 2005
Posts: 21
Location: Sweden
|
| Posted: Thu Mar 16, 2006 12:40 pm Post subject: |
|
|
i got the same error..
it ended on last phase.. when i then later mounted it says
/dev/map/lvol0 527G 218G 309G 42% /mnt/site
filserver / # du -sh /mnt/site/
413G /mnt/site/
df says 218gb used and du 413.. why??
have runned fchk.ext3 alot of times bit nothing happens..
i dunno what version of glibc i used or fschk.. i have now uppgraded gcc then rebuild glibc and gonna restart the computer to se if thats helps...
please anyone have an solution on have to fix this error so it shows right size? Im afraid that if i use the disks i will loose my data on it. |
|
| Back to top |
|
|
moja
n00b
Joined: 04 Feb 2005
Posts: 21
Location: Sweden
|
| Posted: Thu Mar 16, 2006 12:55 pm Post subject: |
|
|
My error is solved..
Uppraded GCC to 3.4.5 and then reemerged and uppgraded glibc. thah reron fschk and rebootet the box.. |
|
| Back to top |
|
|
|
Other Things Gentoo
