Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Jan 1998 17:19:49 -0500 (EST)
From:      Chuck <crtb@capecod.net>
To:        chrw <shredder@hack.babel.dk>
Cc:        freebsd-isp@freebsd.org
Subject:   Re: recovering tar archieve / ssh
Message-ID:  <Pine.FBS.3.93.1.980108170741.1518C-100000@capecod.net>
In-Reply-To: <Pine.BSF.3.95.980108162510.4963A-100000@hack.babel.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
Sounds familiar.  I have a FreeBSD 2.2.2 PC, Tomato, with a TR4 (SCSI)
drive named nrst0.  I run dump on it whenever I feel like it, and have
restored files from way down the tape.  It goes from one end to the other,
then turns around and goes the other way.  I don't know how many tracks
there are --it takes quite a few end-to-end trips-- but it works.

But, when I run dump over the (thinwire) Ethernet from my other
FreeBSD 2.2.2 PC, Daisy, to the same nrst0 via rmt, first, it hiccups
about every two seconds, and averages about 50 kBps.  *** AND *** it
only goes to the end of the tape once and does not turn around.  It says
that Tomato's operator should mount a fresh tape.  This in spite of dump's
-a option.

So I've taken to running dump from Daisy to a BIG file on Tomato, and
then writing that file to tape using dd.  Very fast.

        Chuck Bacon -- crtb@capecod.net
                ABHOR SECRECY -- DEFEND PRIVACY

On Thu, 8 Jan 1998, chrw wrote:

> 
> Hello,
> 
> I hope someone can help me out or give me a hint on the following
> problem. I thought i finally had a working effective way of makign backups
> using tar, with several machines located physically away from my
> office, using a single streamer mounted on a host on my desk.
> 
> Ive been using tar thru an ssh pipe to the fbsd streamer host, like
> 
> tar cvfpl - * | ssh -c blowfish molly 'cat > /dev/nrst0' 
> 
> everything seemed to work fine, but today i tried doing a desaster
> recovery test.. It start extracting fine, but after 1 or 2 mins tar
> terminates with "tar: Unexpected EOF on archive file" :(
> 
> this is defintly NOT good. Its a brand new tape. I havent tried with
> another tape so far, could be a bad tape? (yeah, when u cant explain why
> things go wrong, blame it on the hardware).. 
> 
> the setup is, im doing backup from several sgi servers, onto the freebsd
> streamer host. I cant see this should be a problem.
> 
> Anyway, EVEN if it is a tape error, i cannot rest assure that my backups
> are good untill i have to verified every single tape i got :(
> 
> Maybe tar can verify each archieve it makes automatically, in the
> future..? Ill go check the man page.
> 
> 
> Anyone have any hints or comments?
> 
> Christoffer Walther
> Unix Admin 
> PROVENTUM





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.FBS.3.93.1.980108170741.1518C-100000>