HP3000-L Archives

November 1998, 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:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Mon, 9 Nov 1998 15:20:07 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Pete writes:

> Besides user files, there are other structures on discs which cannot be
> handled by "file moving" software. These structures include freespace

Yep...that's why the MPEX "move off" approach failed.

> maps, label table files, directory files, Transaction Manager files, and
> transient space (last is only on MPEXL_SYSTEM_VOLUME_SET discs; I really
> hate that long name).

Hey...I suggested, years ago, that HP enhance MPE to allow $SYS as
a synonym.  Wouldn't be hard to do, either.  :)

> BUT, be aware that this
> may well be time wasted. If you are replacing a drive you obviously
> have a problem with it and you need to be very aware of exactly what
> that problem is and treat it appropriately. If you are getting
> CORRECTABLE data errors on the drive or head positioning errors which
  ^^^^^^^^^^^
> the drive is handling okay for now, then doing a disc copy is probably
> going to work fine.

Yes...that's the key.  The disk has to be readable for the copy
approach to work.

> HOWEVER, if the problem with the drive has caused any kind of data
> corruption then you should go to your back-up tapes or at least
> understand that there is a very good possibility you have undetected
> data corruption in files and system structures. You will likely spend

You might have undetected data corruption of file data in your backups,
too :)

--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html

ATOM RSS1 RSS2