Dump reports negative disk size
When I run amdump, the following message appears (presumably due to the hard drive being too big): The system is FreeBSD 4.0, with Amanda 2.4.2p2. thanks, Ross. FAILED AND STRANGE DUMP DETAILS: /-- xxx /exports/mail lev 0 FAILED [/sbin/dump returned 3] sendbackup: start [xxx.xxx.net.au:/exports/mail level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/sbin/restore -f... - sendbackup: info end | DUMP: Date of this level 0 dump: Wed Nov 28 12:42:34 2001 | DUMP: Date of last level 0 dump: the epoch | DUMP: Dumping /dev/rmlxd0c (/exports/mail) to standard output | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 22194864 tape blocks. | DUMP: dumping (Pass III) [directories] | DUMP: dumping (Pass IV) [regular files] | DUMP: 1.60% done, finished in 5:07 ? DUMP: read error from /dev/rmlxd0c: Invalid argument: [block -225809704]: count=7168 ? DUMP: read error from /dev/rmlxd0c: Invalid argument: [sector -225809704]: count=512 ? DUMP: read error from /dev/rmlxd0c: Invalid argument: [sector -225809703]: count=512 ? DUMP: read error from /dev/rmlxd0c: Invalid argument: [sector -225809702]: count=512 ? DUMP: read error from /dev/rmlxd0c: Invalid argument: [sector -225809701]: count=512 ? DUMP: read error from /dev/rmlxd0c: Invalid argument: [sector -225809700]: count=512
DDS3 Stacker
Hi all, I am using amanda with an HP Surestore 24x6 DDS-3 autoloader. Amanda is working well with this configuration, except that tape one is problematic, especially when moving from tape 6 to tape 1. Surprisingly, moving from say tape 3 to tape 1 seems to work more reliably. I've tried various new tapes, but it still fails. has anyone else had this problem, or do I have a dodgy piece of hardware? thanks, Ross.
amplot
Does anybody use the graphical capabilities of amanda (i.e. amplot)? I wonder if it is worth using this feature. Regards, Ross.