> This message says taper was linking through the multiple holding disk
> chunks of the backup image of /common/intranet and one of them apparently
> has garbage in its header.
>
> Are you running amdump or amflush when this happens?
amdump, when i run amflush (only on days i haven't been here and no one
changes the tape) if the directory hasn't been backed up i get:
192.168.1.11 -n/intranet NO FILE TO FLUSH
-----------------------------
192.168.1.11 /etc NO FILE TO FLUSH
-----------------------------
192.168.1.11 /var/named NO FILE TO FLUSH
-----------------------------
>
>
> If amflush, what's in your holding disk? Did anything odd happen when the
> dump happened into the holding disk, like file system full or anything
> like that? Can you just remove the holding disk chunks for this disk
> and force it to do a level 0 again on the next amdump run?
nothing odd happening, here's a df -k:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda8 256667 31465 211950 13% /
/dev/hda1 23302 3250 18849 15% /boot
/dev/hda6 4245640 1209460 2820512 30% /home
/dev/hda5 4245640 389700 3640272 10% /usr
/dev/hda7 256667 27428 215987 11% /var
/dev/hdd 14785660 2534400 11500176 18% /common
my disklist for this machine is:
192.168.1.11 /common/intranet
192.168.1.11 /var/named
192.168.1.11 /etc
and my holding disk is /common/amanda
could it be confused because i'm using the same partition (but a separate
directory) to back up?
currently there is nothing in the holding disk, i flushed it this morning &
got the above message. this is the local machine that the amanda server
resides on. it is able to back up the clients over the ethernet fine...
i have 2 tapes & run level 0 every night. it fails on either tape with the
same error.
thanks,
w
>
>
> >walt
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
