On Fri, 30 Nov 2001 at 10:14pm, harald wrote > still got problems got my Seagate IDE Streamer worked with amanda.
>From the output below, the tape drive isn't even part of the equation yet. If you're worried about whether or not it's working, tar some stuff to it by hand. But amanda hasn't even tried to write to tape yet. > FAILURE AND STRANGE DUMP SUMMARY: localhost /mnt/hda9/install lev 0 FAILED > [missing result for /mnt/hda9/install in localhost response] > > > STATISTICS: Total Full Daily -------- -------- ------- > Estimate Time (hrs:min) 0:00 > Run Time (hrs:min) 2:03 Dump Time (hrs:min) 0:00 0:00 0:00 Output Size (meg) > 0.0 0.0 0.0 Original Size (meg) 0.0 0.0 0.0 Avg Compressed Size (%) -- -- -- > Filesystems Dumped 0 0 0 Avg Dump Rate (k/s) -- -- -- > > Tape Time (hrs:min) 0:00 0:00 0:00 Tape Size (meg) 0.0 0.0 0.0 Tape Used (%) > 0.0 0.0 0.0 Filesystems Taped 0 0 0 Avg Tp Write Rate (k/s) -- -- -- So, amanda ran for two hours, and generated *no* dump images (thus nothing to put on tape). From the summary above, it didn't get an estimate for /mnt/hda9/install. The two hours indicates that you're hitting a timeout for the estimates. You can raise 'etimeout' in amanda.conf, but something else is probably wrong. Is /mnt/hda9/install a local filesystem? If it is, what type of disk is it, and are you seeing any errors in the system logs? If it isn't (e.g. if it's NFS mounted), then you should really put amanda on the system hosting the FS. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
