The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Arthur Krewat <krewat@kilonet.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Someone wants to use an exabyte
Date: Wed, 27 Nov 2019 15:56:10 -0500	[thread overview]
Message-ID: <c7bd77e5-c681-6190-1916-c75559c8305b@kilonet.net> (raw)
In-Reply-To: <20191127204311.448C393D8C@minnie.tuhs.org>

On 11/27/2019 2:31 PM, John Foust wrote:
> I couldn't get any of the DDS-2 to read, either on the original hardware that wrote them, or on a newer STD28000N drive I bought on eBay, a pull from an old Apple server. I could write new tapes on the drive, just couldn't read any old ones. My attempts included reading some tapes I know I'd received from other people (that is, written on other drives) that I know I had been able to read on this hardware back in the day. They wouldn't read, either.
That sounds like a block size issue. Usually telling dd to use a larger 
block than the tape has is fine, but if the default is smaller than 
what's on the tape, it'll fail.

Depending on the drive firmware, the OS support for that particular 
drive, etc, you may or may not get warnings or errors that actually mean 
anything.

A long time ago, I attempted to read some 9-track TOPS-10 tapes using a 
Sun and a 6250 BPI capable tape drive. Nothing would read, it looked 
like there were actually no files on the tape whatsoever. So I gave up, 
but kept the tapes because they contained a lot of personal stuff I had 
done in high school and a few years after.

Years later, I got my hands on a Sun3/280 with 9-track tape drive, and 
attempted to read them again. Same thing, looked like there were no 
files on the tape. Started increasing the block size, and VOILA, got data.

Very odd circumstance, but block size has a lot to do with trying to 
read tapes. QIC-150, 8mm, 9-track, I've run into it a lot.

art k.



  reply	other threads:[~2019-11-27 20:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 22:39 Richard Salz
2019-11-24 22:50 ` Jim Capp
2019-11-24 22:52 ` Larry McVoy
2019-11-24 22:58   ` Rico Pajarola
2019-11-24 23:45     ` Clem Cole
2019-11-25  1:41   ` Dave Horsfall
2019-11-25  1:42     ` George Michaelson
2019-11-25  3:24       ` Larry McVoy
2019-11-25 17:07         ` Al Kossow
2019-11-25 17:40           ` Arthur Krewat
2019-11-25 17:45             ` Larry McVoy
2019-11-25 17:49               ` Jon Steinhart
2019-11-25 18:34               ` Arthur Krewat
2019-11-25 21:08                 ` John P. Linderman
2019-11-25 21:11                   ` ron
2019-11-25 21:30                     ` John P. Linderman
2019-11-25 21:38               ` Dave Horsfall
2019-11-25 18:29           ` Warner Losh
2019-11-25  3:29       ` Dave Horsfall
2019-11-25  3:34         ` [TUHS] Someone wants to use an exabyte [ really bulk erasing ] Jon Steinhart
2019-11-25  3:59           ` William Pechter
2019-11-25 15:25             ` Clem Cole
2019-11-25 17:13               ` Al Kossow
2019-11-25  4:53           ` Dave Horsfall
2019-11-25  3:36         ` [TUHS] Someone wants to use an exabyte Larry McVoy
2019-11-25 22:34           ` Dave Horsfall
2019-11-26  1:38             ` Lawrence Stewart
2019-11-25 22:46           ` Dennis Boone
2019-11-25 22:57           ` Henry Bent
2019-11-27 19:31   ` John Foust
2019-11-27 20:56     ` Arthur Krewat [this message]
2019-11-27 21:25       ` Dave Horsfall
2019-11-25 18:12 Norman Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c7bd77e5-c681-6190-1916-c75559c8305b@kilonet.net \
    --to=krewat@kilonet.net \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).