[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re:19990721: COMET case study tar files

>Date:19990723
>Organization:NOAA
>Keywords:199907211628.KAA25831 COMET case study tar files

Hello Greg,

It is curious that the README and install files untarred while the data
did not. Since you were successful with those two files it appears as if
your device is operating properly, even in the medium density command
realm. I fear the tape may have been corrupted in transfer (magnets, heat
etc.) I propose we send you another tape. Are you under strict time
constraints for this data? The postal time should be 2-4 days. If there
are particular datasets you would like to get to in the interim, you can
download them individually from our website. I know this is not the
preferrred method, especially when the entire case is desired, but it may
help you until the new tape arrives. Should we send it to:

465 Weathervane
Calera, AL
35040-5427

Sorry about the difficulties,


Jeff Weber
Unidata/COMET Case Studies
University Corporation for Atmospheric Research

address@hidden
PH:303-497-8676   
URL--http://www.unidata.ucar.edu/staff/jweber

On 23 Jul 1999, Greg Machala wrote:

> 
> In our /dev/rmt directory the only option is for medium density (0mn, 0mnb, 0m
> etc).  There are some other device files that look like c0t3d0BEST(n,b) as 
> well.
>  I tried them all but all of them yield the same error 
> "tar:errror reading from tape"
> 
> Is there some way to get a device file to read different tape density?
> 
> GREG
> 
> ____________________Reply Separator____________________
> Subject:    19990721: COMET case study tar files
> Author: address@hidden
> Date:       7/21/99 2:30 PM
> 
> >Date:19990721
> >Organization:NOAA
> >Keywords:199907211628.KAA25831 COMET case study tar files
> 
> Hello Greg,
> 
> I believe we may have a density issue at work here.
> Our tapes are available in both low-density and high-density formats.
> The commands /dev/rmt/0mb -or- /dev/rmt/0mnb are both indicating
> medium density [ the m in /0mnb ]. I suggest you try either an l(for low
> density) or an h(for high density) depending on the format the tape was
> made in. The high density is the default so you may want to try that first
> unless you specified low density at the time of the order. The b is also
> optional in this command, but I do not think it should impact the
> untarring of files. I hope this works for you, if not please write back
> with as much info on the error messages that you receive.
> 
> 
> Jeff Weber
> Unidata/COMET Case Studies
> University Corporation for Atmospheric Research
> 
> address@hidden
> PH:303-497-8676
> URL--http://www.unidata.ucar.edu/staff/jweber
> 
> On Wed, 21 Jul 1999, Unidata Support wrote:
> 
> >
> > ------- Forwarded Message
> >
> > >To: address@hidden
> > >From: Greg Machala <address@hidden>
> > >Subject: Re. COMET case study tar files
> > >Organization: NOAA
> > >Keywords: 199907211628.KAA25831 COMET case study
> >
> >
> >     I have gotten a tap archive of data from Mar of 1993, basically .gem 
> > files
> > sat pics and radar pics.  I am fast forwarding the tape as per the
>  instructions
> > but I keep getting a tar tape read error when I try untarring files from the
> > tape.  I was able to untar the README.INSTALL and install.ps files but
>  anything
> > beyond that on the tape give the tar tape read error.  This is an
> > HP machine with and Andataco 8mm tape drive /dev/rmt/0mb -or- /dev/rmt/0mnb
>  for
> > no rewind.
> > Any ideas?
> >
> > address@hidden
> >
> >
> > ------- End of Forwarded Message
> >
> >
>