Amanda-Users

Re: odd behavior after adding DLE

2006-12-22 09:32:05
Subject: Re: odd behavior after adding DLE
From: Jean-Louis Martineau <martineau AT zmanda DOT com>
To: Joel Coltoff <joel AT wmi DOT com>
Date: Fri, 22 Dec 2006 09:20:35 -0500
You hit a known bug in 2.5.p1 with parsing the disklist file, it is fixed in 2.5.1p2.

I didn't remember the detail, but try 2.5.1p2

Jean-Louis

Joel Coltoff wrote:
Hi,

I added a new DLE today

    cluster1-node1.wmi.com /services /services {
        system-files
    } 1 local

Along with the dumptype in amanda.conf (a work in progress)

    define dumptype global {
        comment "Global definitions"
        index yes
    }
    define dumptype system-files {
        program "GNUTAR"
        global
        comment "High priority"
        priority high
    }

The DLE was right at the top of the disklist file.

If I run "amadmin Daily disklist" I get some of the
expected output plus the following:

*** glibc detected *** double free or corruption (fasttop): 0x09af6698 ***
Abort

If I move the new DLE elsewhere in the file I see no hint that there
is a problem.

amanda version: 2.5.1p1

uname -a:
Linux cluster1-node1.wmi.com 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST 2006
i686 i686 i386 GNU/Linux

gcc -v:
  gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)

Any ideas what is causing this? Is there a something that gets missed
when the DLE moves?

I've looked a bit at the forums list at zmanda and other have seen this when doing dumps. I'm guessing all we do here is some parsing and perhaps some high level checking. i.e. it shouldn't matter which version of tar I use. (1.13.25)

Thanks,
 - Joel





<Prev in Thread] Current Thread [Next in Thread>