HP3000-L Archives

November 1997, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Guy Smith <[log in to unmask]>
Reply To:
Guy Smith <[log in to unmask]>
Date:
Mon, 10 Nov 1997 08:40:20 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
On Monday, November 10, 1997 1:31 AM, Lars Appel
[SMTP:[log in to unmask]] wrote [in part]:
> Haven't done it myself so far, but might copy faster than via DDS.
> I also do not know how COPYVOL behaves when old disc gives media read
> errors during the copy operation...
>
> Lars (anybody "been there, done that"?)

Yep.  Long ago, in a different life (on a small, uncharted planet in the .
. .).

We had a disc crash (old Eagle drive), and it marred the area of the disc
where the volume label was.  The drive still worked, and MPE would try to
bring it online.  However, during the mount process, MPE tries to update
the volume label.  When it tried, and failed due the media being trashed,
it would quit the mount operation.

Well, this was a huge volume set and production was waiting.  We had just
swapped out some other Eagles and had spares sitting on the floor, so we
hooked one up and ran COPYVOL.  It read the entire pack without problems
(including the volume label) and MPE only had one hissy fit when we brought
the new volume online (a sys abort I think, followed by normal operations).

Even though COPYVOL is slower than me without my morning coffee, it was
better than reloading the entire volume set and rerunning batch.

Guy Smith

ATOM RSS1 RSS2