> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie
> Sent: Monday, February 26, 2007 12:17 PM
> To: [email protected]
> Subject: Re: AMANDA 2.51p*3* and gtar 1.16.1 and error 2
>
> On Mon, Feb 26, 2007 at 11:28:04AM -0500, Mark Hennessy wrote:
> > Sorry for the delay in this e-mail being delivered to the
> list. I had
> > originally tried to send it on
> > 16 Feb 2007.
> >
> > --
> > Mark Hennessy
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Mark Hennessy
> > > Sent: Monday, February 26, 2007 9:29 AM
> > > To: [email protected]
> > > Subject: RE: AMANDA 2.51p*3* and gtar 1.16.1 and error 2
> > >
> > > Here's my disklist entry for the gtar backup disk in question:
> > > # Dumptypes for gnutar
> > > define dumptype root-tar {
> > > global
> > > program "GNUTAR"
> > > comment "root partitions dumped with tar"
> > > compress none
> > > estimate calcsize
> > > index
> > > exclude list "/usr/local/etc/amanda/Backup/exclude.gtar"
> > > priority low
> > > }
> > >
> > > exclude.gtar is a zero-byte file.
> > >
> > > --
> > > Mark Hennessy
> > >
> > > > Subject: Re: AMANDA 2.51p*3* and gtar 1.16.1 and error 2
> > > >
> > > > On Fri, Feb 16, 2007 at 12:25:54PM -0500, Mark Hennessy wrote:
> > > > > >
> > > > > > Mark, looking at the gnutar code shows the message
> > > > "memory exhausted"
> > > > > > in about 3 locations. One that I noted was the
> pattern matching
> > > > > > compiler (regcomp). Do you use a lot of
> > > include/exclude patterns
> > > > > > on this DLE?
> > > > > >
> > > > >
> > > > > AFAIK, I haven't explicitly defined any patterns at all.
> > > > Where would these
> > > > > be set?
> > > > >
> > > > > Mark Hennessy
> > > >
> > > > In disklist.
> > > >
> > > > Check your settngs with:
> > > >
> > > > amadmin <config> disklist <host> <dle_name>
> > > >
>
> Well, the exclude/include/RE idea was just a thought after
> scanning the gtar source code.
>
> Only thing I note in your disklist, which is not likely
> related, is you have no argument
> to the index parameter. That should be a boolean, yes/no.
>
> BTW the reason I suggested you show your disklist entry with
> amadmin is that most
> dumptypes include other dumptype entries. For example, your
> the "root-tar" dumptype
> you show includes your "global" dumptype as well. We have no
> idea what settings are
> in "your" global dumptype. It is unlikely they are causing
> your problem, but we
> don't know when we don't see them.
>
> I presume that you problem continues after the week long interval.
>
> --
> Jon H. LaBadie [EMAIL PROTECTED]
> JG Computing
> 4455 Province Line Road (609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
>
>
Global has no active settings at all at present.
define dumptype global {
comment "Global definitions"
# This is quite useful for setting global parameters, so you don't have
# to type them everywhere. All dumptype definitions in this sample file
# do include these definitions, either directly or indirectly.
# There's nothing special about the name `global'; if you create any
# dumptype that does not contain the word `global' or the name of any
# other dumptype that contains it, these definitions won't apply.
# Note that these definitions may be overridden in other
# dumptypes, if the redefinitions appear *after* the `global'
# dumptype name.
# You may want to use this for globally enabling or disabling
# indexing, recording, etc. Some examples:
# index yes
# record no
# split_diskbuffer "/raid/amanda"
# fallback_splitsize 64m
}
--
Mark Hennessy
