Hi,
you tell us your holding-area is located on /home/amanda/tmp, right?

completly from your backup.
it is very bad to backup a filesystem containing the holdingdisk itself
with a dumptype not excluding this area or not having the nohold option
set.
it will produce tons of data-waste in theimage for the partition,
if it doesn't fail at all.
Christoph

Dalton, John L MONMOUTH ITS Multimax wrote:

I fixed this by putting it in the exclude list
and amdump was happy - no more errors.

I do not think I need this file anyway since it is part
of the holding disk???


-----Original Message-----
From: Gene Heskett [mailto:gene.heskett AT verizon DOT net]
Sent: Friday, August 15, 2003 3:34 PM
To: Dalton, John L MONMOUTH ITS Multimax; 'amanda-users AT amanda DOT org'
Subject: Re: How can I fix this as it is failing the backup!!

On Friday 15 August 2003 10:59, Dalton, John L MONMOUTH ITS Multimax wrote:

FAILED AND STRANGE DUMP DETAILS:

/-- XXXXXX    /home lev 2 STRANGE
sendbackup: start [XXXXXX:/home level 2]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./amanda/tmp/20030815/XXXXXX._home.2.tmp: file changed as we
read it

| Total bytes written: 234874880 (224MB, 5.9MB/s)

sendbackup: size 229370
sendbackup: end

I don't imagine you can unless you can stop the activity in the /home filesystem while amanda is running.