View Full Version : amcheck Problem

August 11th, 2006, 07:36 AM
Greetings again,

This is my first full week testing Amanda 2.5.0p2. Yesterday amcheck reported:

*** glibc detected *** /usr/sbin/amcheck: double free or corruption (fasttop): 0x08141e80 ***
======= Backtrace: =========
======= Memory map: ========
Amanda Tape Server Host Check
Holding disk /d2/space/amandahold: 66395160 kB disk space available, that's plenty

Amanda Backup Client Hosts Check
Client check: 4 hosts checked in 4.562 seconds, 0 problems found

(brought to you by Amanda 2.5.0p2)

I'm thinking it was because the magazine was on the last tape and needed more room? Maybe..but I doubt this is a normal error.

I have ejected that magazine, cleared the DB and ready to start over tonight. Any suggestions?


August 11th, 2006, 10:55 AM
It is difficult to guess why glibc detected memory allocation problems in amcheck with
the stack trace.

2.5.1b2 has lots of memory management fixes and we have used valgrind to resolve
many such problems. If you are ok, you can try 2.5.1b2.

Otherwise, you can try if the problem goes away tonight. BTW, glibc memory problem
detection may not cause amanda programs to fail. Did your backup succeed?


February 13th, 2007, 01:47 AM

I have same problem, I found it because the system could not detect the tape-media such as tape-cleaner or damaged tape.

After replacing the tape, the system work just fine.