Now I have another problem, the dump fails at the end ...
I am dumping a 8 Gbyte partition and I have a DDS2 Tape drive so I
dump to 4Gb tapes.
Here is the email I get back:
These dumps were to tape DailySet104.
*** A TAPE ERROR OCCURRED: [[cannot overwrite active tape DailySet104]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next 2 tapes Amanda expects to used are: a new tape, a new
tape.
FAILURE AND STRANGE DUMP SUMMARY:
bluesky sd0s1f lev 0 FAILED ["data write:
Broken pipe"]
bluesky sd0s1f lev 0 FAILED [out of tape]
bluesky sd0s1f lev 0 FAILED [dump to tape
failed]
STATISTICS:
Total Full
Daily
-------- -------- --------
Estimate Time (hrs:min) 0:00
Run Time (hrs:min)
2:08
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) --
-- --
FAILED AND STRANGE DUMP DETAILS:
/-- bluesky sd0s1f lev 0 FAILED ["data write:
Broken pipe"]
sendbackup: start [bluesky:sd0s1f level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/sbin/restore -f...
-
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Date of this level 0 dump: Wed Jun 6
09:17:13 2001
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/rsd0s1f (/usr) to standard output
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 6702047 tape blocks.
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
| DUMP: 3.33% done, finished in 2:25
| DUMP: 7.39% done, finished in 2:05
| DUMP: 10.57% done, finished in 2:06
| DUMP: 13.43% done, finished in 2:08
| DUMP: 16.07% done, finished in 2:10
| DUMP: 18.61% done, finished in 2:11
| DUMP: 22.64% done, finished in 1:59
| DUMP: 26.01% done, finished in 1:53
| DUMP: 29.09% done, finished in 1:49
| DUMP: 33.17% done, finished in 1:40
| DUMP: 36.33% done, finished in 1:36
| DUMP: 39.61% done, finished in 1:31
| DUMP: 42.91% done, finished in 1:26
| DUMP: 46.48% done, finished in 1:20
| DUMP: 49.19% done, finished in 1:17
| DUMP: 51.87% done, finished in 1:14
| DUMP: 54.55% done, finished in 1:10
| DUMP: 57.72% done, finished in 1:05
| DUMP: 60.47% done, finished in 1:02
| DUMP: 62.51% done, finished in 1:00
| DUMP: 64.84% done, finished in 0:56
| DUMP: 68.62% done, finished in 0:50
| DUMP: 72.74% done, finished in 0:43
| DUMP: 75.40% done, finished in 0:39
\--------
NOTES:
planner: Adding new disk bluesky:sd0s1f.
taper: tape DailySet104 kb 3344032 fm 1 writing file: Input/output
error
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISK
L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-------------------------- --------------------------------- ------------
bluesky sd0s1f
0 FAILED ---------------------------------------
(brought to you by Amanda version 2.4.2p2)
Is it a real problem of tape size ? Is it configuration problem ??
Thanks again for helping.
Pat.
Alexandre Oliva wrote:
On Jun 5, 2001, Patrick Ellis <[EMAIL PROTECTED]> wrote:> I just installed amanda version 2.4.2p2 on a FreeBSD node and I have
> amandad: version 2.3.0Look, you're running 2.4.2p2's amcheck but the client is still running
2.3.0's amandad. The protocol was modified in release 2.4.0, and it's
no longer compatible with that of 2.3.0. You have to upgrade all the
clients to 2.4.* when you upgrade the server to 2.4.*.--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
