HP3000-L Archives

August 1997, Week 3

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:
mike hornsby <[log in to unmask]>
Reply To:
mike hornsby <[log in to unmask]>
Date:
Fri, 15 Aug 1997 12:05:08 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
>>We are adding a new disk to our system volume set and a couple of new
disks
>>to another volume set.  After installing the disks, would it be best to:
>>1. Reload all the data from tape? or
>>2. Spread the data to the new disks using Bradmark's Disk Space Manager?


Your message doesn t say if you were simply adding discs for more space, or
if disc IO was a problem in the first place. In either event I would never
suggest adding discs with out first testing them by adding them as a dummy
volume set and restoring /copying data to them. It won t play very well to
users and management if one of these discs fails and you can t say that you
tested them before making them production.

Prior to the adding of passwords to the diagnostics it was possible to
perform a write error test of discs. Please lets not start a long thread
about it, just suffice it to say that any OS should provide a method to
error test disc drives.

As for the issue of spreading the data, this would only be of value if the
system is IO bound to begin with and you could actually achieve a spread of
the busy files across the discs. Otherwise, you are just wasting time and
money.

[log in to unmask]

ATOM RSS1 RSS2