glibc detected *** usmb: double free or corruption

1227487318000

Anyone would be concerned by an error message like the one above. Not me. I've been there done it and know that it's a not a big issue. if you do a google you will find all kinds of lame suggestions. This is really nothing to worry about. The first time I ran into it was nearly four years ago when I accidentally loaded both PHP4 and PHP5 modules into apache. The error was something like *** glibc detected *** double free or corruption: 0x0811fd30 *** This time I was working with a Qemu image that was on a remote machine. An image that was accessed through a samba share. I was playing with some firewall rules while the virtual machine was running and it appeared to get stuck. When I tried to shutdown the VM and relaunch it Qemu told me that it 'could not open disk image'  and ls said:

ls: cannot open directory .: Transport endpoint is not connected

Then I thought to mount the samba share again with usmb. That's when the error popped up.
fuse: bad mount point `/mnt/radmedia': Transport endpoint is not connected
*** glibc detected *** usmb: double free or corruption (!prev): 0x00000000008ea1e0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3737a78228]
/lib64/libc.so.6(cfree+0x76)[0x3737a7a866]
usmb[0x403925]
usmb[0x402904]
usmb[0x402b78]
/lib64/libc.so.6(__libc_start_main+0xfa)[0x3737a1e32a]
usmb[0x401d99]
Immidiately I realized this might be caused by an internal conflict and thought of unmounting the samba share (even though the system told me it's no longer mounted). fusermount -u /mnt/radmedia was all it took to solve this.  (/mnt/radmedia being my mount point). Now the smb share has been remounted and the virtual machine is running once again.
comments powered by Disqus