Re: tape dump errors -- what does it mean?
2002-08-04 00:22:34
On Sat, Aug 03, 2002 at 08:13:06PM -0500, Keith Clay wrote:
> Folks,
>
> I started amdump and this is what I got:
>
> >These dumps were to tape wipSet10004.
> >*** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
> >Some dumps may have been left in the holding disk.
> >Run amflush to flush them to tape.
> >The next tape Amanda expects to use is: a new tape.
> >
> >FAILURE AND STRANGE DUMP SUMMARY:
> > clayk / lev 0 FAILED [out of tape]
> >
> >
> >STATISTICS:
> > Total Full Daily
> > -------- -------- --------
> >Estimate Time (hrs:min) 0:00
> >Run Time (hrs:min) 0:43
> >Dump Time (hrs:min) 0:27 0:27 0:00
> >Output Size (meg) 1718.9 1718.9 0.0
> >Original Size (meg) 4080.1 4080.1 0.0
> >Avg Compressed Size (%) 42.1 42.1 --
> >Filesystems Dumped 4 4 0
> >Avg Dump Rate (k/s) 1101.2 1101.2 --
> >
> >Tape Time (hrs:min) 0:13 0:13 0:00
> >Tape Size (meg) 670.5 670.5 0.0
> >Tape Used (%) 3.4 3.4 0.0
> >Filesystems Taped 3 3 0
> >Avg Tp Write Rate (k/s) 884.2 884.2 --
> >
> >
> >NOTES:
> > planner: Adding new disk clayk:/.
> > planner: Adding new disk clayk:/boot.
> > planner: Adding new disk clayk:/home.
> > planner: Adding new disk clayk:/usr/local.
> > driver: WARNING: /clayk: 5242880 KB requested, but only 4755116 KB
> > available.
> > taper: tape wipSet10004 kb 1468256 fm 4 writing file: Input/output error
> > driver: going into degraded mode because of tape error.
> >
> >
> >DUMP SUMMARY:
> > DUMPER STATS TAPER STATS
> >HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
> >-------------------------- --------------------------------- ------------
> >clayk / 0 29919001073632 35.9 17:251027.4 N/A N/A
> >clayk /boot 0 16040 9568 59.7 0:051744.4 0:14 681.2
> >clayk /home 0 1039350 629024 60.5 8:141274.1 11:43 894.6
> >clayk /usr/local 0 130740 47904 36.6 0:54 883.6 0:59 809.5
> >
> >(brought to you by Amanda version 2.4.2p2)
>
>
> I ran amflush and got this:
>
>
> >The dumps were flushed to tape wipSet10001.
> >The next tape Amanda expects to use is: a new tape.
> >
> >FAILURE AND STRANGE DUMP SUMMARY:
> > taper: FATAL error [file_reader_side cmd 0 argc 0]
> > taper: FATAL syncpipe_get: w: unexpected EOF
> >
> >
> >STATISTICS:
> > Total Full Daily
> > -------- -------- --------
> >Estimate Time (hrs:min) 0:00
> >Run Time (hrs:min) 0:20
> >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:16 0:16 0:00
> >Tape Size (meg) 1048.5 1048.5 0.0
> >Tape Used (%) 5.3 5.3 0.0
> >Filesystems Taped 1 1 0
> >Avg Tp Write Rate (k/s) 1092.0 1092.0 --
> >
> >
> >NOTES:
> > taper: tape wipSet10001 kb 1073664 fm 1 [OK]
> >
> >
> >DUMP SUMMARY:
> > DUMPER STATS TAPER STATS
> >HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
> >-------------------------- --------------------------------- ------------
> >clayk / 0 29919001073664 35.9 N/A N/A 16:231092.0
> >clayk /boot NO FILE TO FLUSH -----------------------------
> >clayk /home NO FILE TO FLUSH -----------------------------
> >clayk /usr/local NO FILE TO FLUSH -----------------------------
> >
> >(brought to you by Amanda version 2.4.2p2)
>
>
>
> What does this mean? What is the problem?
>
>>> End of included message <<<
Looks like a first run, thus level zero's must be done of each file system.
Your tape is not big enough to fit level zero's of all four file systems.
The one that did not fit was flushed to the second tape.
Only thing unclear is:
> >FAILURE AND STRANGE DUMP SUMMARY:
> > taper: FATAL error [file_reader_side cmd 0 argc 0]
> > taper: FATAL syncpipe_get: w: unexpected EOF
For that check your debug files, probably in /tmp/amanda, for more info.
A guess is that it did not affect the flush but happened at the very end.
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
|
|