On Mon, Jun 12, 2006 at 08:28:26PM +0200, Kristian Rink wrote:
>
> Hello John, all:
>
> and at first thanks for your comments...
>
>
> Jon LaBadie schrieb:
> >> to have completed without errors, but, running amverify ended up with
> >> the following:
> >
> > This is just guesswork, given that I'm bad and don't run amverify.
>
...
>
> >> amverify Full
> >> Mo Jun 12 13:01:54 CEST 2006
> ...
> >> Checked backer.planconnect.net.planc1.20060610.0
> >> End-of-Information detected.
> >> Loading next slot...
> >> ...
...
>
> To be a little more verbose on that, here's an excerpt taken from
> yesterdays Full dump log (sizes):
>
>
> [...]
> Output Size (meg) 172568.1 172568.1 0.0
> Original Size (meg) 372550.6 372550.6 0.0
> Avg Compressed Size (%) 46.3 46.3 --
> Filesystems Dumped 7 7 0
> Avg Dump Rate (k/s) 1198.0 1198.0 --
> [...]
> Tape Size (meg) 172568.1 172568.1 0.0
> Tape Used (%) 86.4 86.4 0.0
> Filesystems Taped 7 7 0
> [..]
> USAGE BY TAPE:
> Label Time Size % Nb Nc
> Back00 40:59 176709760k 86.4 7 0
>
>
> I'm not sure right now, but the way I understand this, we did back up
> 372.5 gig of data (which seems reasonable looking at the RAID disk
> usage), compressed to 172.5gig. Assuming that LTO-2 at this level is
> capable of storing 200gig data, the 86.4% usage of that very (single)
> tape do make sense.
>
> This way, the "End-Of-Information" message seems rather obscure... :o
> Any more ideas, anyone? :)
I tried the ultimate documentation, a run of amverify on my own data
and a peek at the amverify source (a shell script).
I think the "End of Information" message is a normal message,
just a notice that it did not necessarily reach the physical
end of the tape (a different part of the source).
On my amverify run (a two vtape amdump run), I got basically the
same information as you reported, including the "EOI" message at
the end of each vtape.
Also, in the source, after the loop running through the tapes
is completed there is a section showing "if the file collecting
defects has anything in it, cat it to the user with the message
"Errors found: " preceeding it. Neither you nor I appear to
have received such a message.
It would be very easy to change that if statement to have an
else clause printing "no errors found". Should you think that
is desireable, submit an RFE to the amanda developers.
--
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)
|
