Computer Old Farts Forum
 help / color / mirror / Atom feed
From: "Michael Kjörling" <e5655f30a07f@ewoof.net>
To: tuhs@tuhs.org
Cc: coff@tuhs.org
Subject: [COFF] Re: [TUHS] Re: reading historic magnetic tapes
Date: Sat, 28 Jan 2023 20:12:14 +0000	[thread overview]
Message-ID: <2c916808-5463-44a5-a89d-cc50e685631a@home.arpa> (raw)
In-Reply-To: <1595e77d-697c-b2e8-5aff-fe63c92f4747@ucsb.edu>

On 28 Jan 2023 11:29 -0800, from frew@ucsb.edu (James Frew):
> As I was leaving the lab late one evening during this mini-crisis, I had to
> walk around a custodian who was busy giving the linoleum floor in the
> hallway its annual deep cleaning / polishing. This involved a dingus with a
> large (~18" diameter) horizontal buffing wheel, atop which sat an enormous
> (like, a cylinder about as big around as a soccer ball) electric motor,
> sparking commutator clearly visible through the vents in the metal housing.

This is probably more COFF than TUHS, but I recall a story from almost
certainly much later where someone (I think it was a secretary; for
now, let's pretend it was) had been told to change backup tapes daily
and set the freshly taken backup aside for safekeeping. Then one day
the storage failed and the backups were needed, only it turned out
when trying to restore the backups that _every_ _single_ _tape_ was
blank. Nobody, least of all the secretary, could explain how that
could have happened, and eventually, the secretary was asked to
demonstrate exactly what had been done every day. Turned out that
while getting the replacement tape, the secretary put the freshly
taken backup tape on a UPS, which apparently generated a strong
magnetic field, before setting that tape aside. So the freshly taken
backup tape was dutifully well and thoroughly erased. Nobody had
mentioned the little detail of not putting the tape near the UPS.

Oops.

-- 
Michael Kjörling                     🏡 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”


       reply	other threads:[~2023-01-28 20:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6778F07B-DD74-4F04-A877-7D3751E96317@quintile.net>
     [not found] ` <1595e77d-697c-b2e8-5aff-fe63c92f4747@ucsb.edu>
2023-01-28 20:12   ` Michael Kjörling [this message]
2023-01-28 20:17 ` [COFF] " Charles H Sauer (he/him)

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=2c916808-5463-44a5-a89d-cc50e685631a@home.arpa \
    --to=e5655f30a07f@ewoof.net \
    --cc=coff@tuhs.org \
    --cc=tuhs@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).