On Thursday 21 December 2006 12:13, 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.
Generally speaking, when amanda sets something up to do, it uses a set of
defaults derived from previous stanza's. My not too well educated guess
is that if none have been established, the really empty options list is
the problem.
This is also a caveat to observe when making a new dumptype in the
amanda.conf, it only reads it once and does not try to resolve what I'd
call for lack of a better name, a forward reference. Said another way,
you cannot re-use a definition unless its been fully defined in the
amanda.conf at a point above the re-use point. So my 'rule of thumb' is
to add anything new to the bottom of the file.
I'm not convinced that the use of two '/services' strings in the disklist
is 100% kosher either. From perusing mine, the first string is the alias
or the FQDN of the machine to be backed up.
The second is the absolute path to be backed up.
The third is the dumptype.
The fourth is the spindle number.
And the 5th is a specifier as to whether its local, or out on the local
network, eg local or le0
Where the use of {} is brought into play, see this stanza in your disklist
if you just added to the default disklist:
#hosta /diskA/ag /diskA {
# # all directories that start with [a-g] except big1 and big2
# high-tar
# include "./[a-g]*"
# exclude "./big1" "./big2"
# } 1
here we see that the dumptype is specified inside the {}, as are the
include and exclude definitions, but that the spindle number is outside
the {}, and I note that there should have been another item after the 1,
either a 'local' or an 'le0' to have it fully specified.
By specifying the spindle number as the same number for everything on a
given disk, you are telling amanda that she cannot parallelize these
backups, but must do them serially in order to keep from pounding the
seek mechanisms excessively.
So by using '/services' twice, technically I believe its correct, but I'd
be wary of unwanted interactions just to be my usual somewhat paranoid
self. But I think the real error is in the order of the dumptype defines
in your amanda.conf.
>
>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
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
|
