Paul,
Again thanks for the shell script. We ran a brand new tape in the machine and
got this output:
====
AMANDA: FILE 20040818 cvs.yadayada.com /etc lev 1 comp"N program /bin/gtar
To restore,"position tape at start of file and run:
dd if=<tape>"bs=32k skip½1"| /bin/gtar -f... -
1+0 records in
1+0 records out
====
AMANDA: FILE 20040818 stats.yadayadayada.com /etc lev 1 comp"N program
/bin/gtar
To restore, position tape at start of file and run:
dd if=<tape>"bs=32k skip½1"| /bin/gtar -f... -
1+0 records in
1+0 records out
====
It looks like I am still getting some strange headers. We were wondering if
this could be due to different releases of amanda running on the various
machines. A couple of
other options are that the tape drive is going bad or that maybe there is some
config setting that needs to be changed. Any ideas?
Scott
----- Original Message -----
From: Paul Bijnens <paul.bijnens AT xplanation DOT com>
Date: Wed, 18 Aug 2004 11:24:07 +0200
To: Scott Frisbie <sfriz AT linuxmail DOT org>
Subject: Re: 'strange amanda header' errors
> Scott Frisbie wrote:
>
> > I've been trying to run amrestore with the following command and I've
> > been getting lots of these errors:
> >
> > amrestore /dev/nst0 SERVER_NAME
> >
> > amrestore: strange amanda header: "AMANDA: FILE 20040810
> > SERVER_NAME /etc lev 1 comp"N program /bin/gtar"
> > amrestore: WARNING: not at start of tape, file numbers will be offset
>
> Is this the exact error message? Or are there ctrl-M's that fold part
> of the line onto the previous one (that double quote in the middle
> of the string 'comp"N' is strange!).
> Or is the header broken off after the letter "p" in "comp"?
>
> To verify just the headers do:
>
> TAPEDEV=/dev/nst0
> mt -f $TAPEDEV rewind
> while mt -f $TAPEDEV fsf 1 ; do
> dd if=$TAPEDEV bs=32k count=1 | tr -d '\0'
> echo "===="
> sleep 1
> done
>
> To avoid the second warning "not at start of tape", always rewind
> the tape before starting amrestore (or position it just before
> the needed image with "mt fsf" and than you know that warning is
> expected).
>
>
> >
> > after which amrestore stops and I run the the command again to get
> > the
> > error message for the next file on the tape. I occasionally get
> > amrestore: 0: restoring SERVER_NAME._path_to_file.20040810.1
> > amrestore: 1: skipping OTHER_SERVER1._path_to_files.20040810.0
> > amrestore: 2: skipping OTHER_SERVER2._path_to_files.20040810.1
> >
> > before getting one of the 'strange amanda header' errors, but it's
> > kind
> > of rare. Is this a sign of tapes going bad? Is there some config file
> > that
> > needs to be fixed? Is there a better way to get the data off the
> > tapes?
>
>
>
>
> --
> Paul Bijnens, Xplanation Tel +32 16 397.511
> Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
> http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT
> com
> ***********************************************************************
> * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
> * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
> * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
> * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
> * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
> * ... "Are you sure?" ... YES ... Phew ... I'm out *
> ***********************************************************************
>
>
--
______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered by Outblaze
|
