We have been having a few problem with the holdingdisk getting full so last
night I cut my backups down to the 4 most important partitions. I also mad them
go straight to tape but when I do a amstatus I get the following:
Using /var/adm/amanda/scms/amdump from Thu Apr 18 22:00:00 BST 2002
arthur:/export/home/grad 1 1718939k dump done (1:59:43), wait
for writing to tape
arthur:/export/home/msc 1 3298934k dump done (5:43:31), wait
for writing to tape
arthur:/export/home/staff 0 5643076k dump done (4:01:32), wait
for writing to tape
arthur:/export/home/student 0 7876122k dumping 0k (5:43:31)
SUMMARY part real estimated
size size
partition : 4
estimated : 4 18606402k
flush : 0 0k
failed : 0 0k ( 0.00%)
wait for dumping: 0 0k ( 0.00%)
dumping to tape : 0 0k ( 0.00%)
dumping : 1 0k 7876122k ( 0.00%) ( 0.00%)
dumped : 3 10660949k 10730280k ( 99.35%) ( 57.30%)
wait for writing: 3 10660949k 10730280k ( 99.35%) ( 57.30%)
wait to flush : 0 0k 0k (100.00%) ( 0.00%)
writing to tape : 0 0k 0k ( 0.00%) ( 0.00%)
failed to tape : 0 0k 0k ( 0.00%) ( 0.00%)
taped : 0 0k 0k ( 0.00%) ( 0.00%)
9 dumpers idle : not-idle
taper writing, tapeq: 0
network free kps: 39638
holding space : 8577695k (100.00%)
dumper0 busy : 4:28:47 (100.00%)
taper busy : 4:28:47 (100.00%)
0 dumpers busy : 0:00:00 ( 0.00%)
1 dumper busy : 4:28:47 (100.00%) not-idle: 4:28:47 (100.00%)
What's the story here, how can student be at 0% since 5.43am when it is now
10am? Has this backup failed? Also if I've got 'holdingdisk no' in the dumptype
for every backup I'm doing so why does the report say the dump is done but
waiting to write to tape? How can it be waiting to write to tape if the dump is
done when I'm not using a holdingdisk?
David Flood
Systems Administrator
