Amanda-Users

Re: tar dumping to /dev/null

2003-09-18 08:45:50
Subject: Re: tar dumping to /dev/null
From: Marc Cuypers <mozilla AT mgvd DOT be>
To: Paul Bijnens <paul.bijnens AT xplanation DOT com>
Date: Thu, 18 Sep 2003 14:43:24 +0200
Paul Bijnens wrote:

Marc Cuypers wrote:

in runtar.*.log I find the following:


Isn't it runtar.*.debug ?

You are right. :-)



running: /bin/tar: /bin/tar --create --file /dev/null --directory /
--one-file-system --listed-incremental
/var/lib/amanda/gnutar-lists/ulysses.lan.publivandyck.besda2_0.new
--sparse --ignore-failed-read --totals .

It seems to me that tar is dumping to /dev/null.


That's the estimate phase: it runs gnutar just to get
the result of --totals.

You should look in sendbackup.*.debug.

There is no sendbackup.*.debug.




diskdir "/tmp/amandadump"       # where the holding disk is
disksize 290 MB         # how much space can we use on it
#diskdir "/dumps/amanda/work" # additionaly holding disks can be specified
#diskdir "/mnt/disk4"
#disksize 1000 MB       #   they are used round-robin



What version of amanda are you using?

I'm using version 2.4.2

AFAIK "diskdir" or "disksize" are not allowed in the amanda.conf
file (or not allowed anymore; was this pre-2.4.0?)
I seem to have documentation of 2.3. Where can I find the one for 2.4, I downloaded the latest version 2.4.4, but this also mentions to put diskdir in amanda.conf.

Marc.


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