HP3000-L Archives

July 1999, 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:
Lee Gunter <[log in to unmask]>
Reply To:
Lee Gunter <[log in to unmask]>
Date:
Wed, 14 Jul 1999 09:42:35 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (69 lines)
You don't need to boot from an SLT to enable a newly configured disk;
however, you must create an SLT with the new configuration at some point.
Whether you do it before or after booting the system with the new config
(START NORECOVERY) is up to you, but don't delay this step.

The volume management piece must be done after the device is mounted.  You
can add the new volume to $SYS (my alias) at any time, but, as Doug Werth
recommended earlier, you should let it spin for as long as you can before
defining the volume.  Also, be aware that all new file extents will land on
the new volume until the percentage full reaches the level of your other
volumes on $SYS, given the volume size and permanent file allocation
percentage for that disk.

============================================================
Lee Gunter                                 Tel: 503.375.4498
Supervisor, TRG HP/MPE Systems            Fax: 503.375.4401
The Regence Group                  E-mail: [log in to unmask]
============================================================
All opinions expressed are just that -- opinions.  They're
mine and mine alone.




From: Bob Comeau <[log in to unmask]> on 07/14/99 09:02 AM

Please respond to Bob Comeau <[log in to unmask]>


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: [HP3000-L] Adding a disk to system volume





<snipped>

I was also unclear about whether I needed to make an SLT with the new drive
configured to boot from or, as you suggest, just make changes in the CONFIG
group and boot from the primary path after the drive is in.

I figured the VOLUTIL stuff couldn't be done before the drive was
physically
present, although some of it seemed like it could be done ahead of time.
Where this drive was being added to the system volume set, I was concerned
that the
system would not boot if all members of the system volume set were not
ready
to
go when bringing the system up after installing the drive, but the new
drive
would
not be ready yet when the system first comes up...   The old chicken and
egg
thing.
Your method seems straight forward enough.

Thanks

Bob


-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Andreas Schmidt
Sent: Wednesday, July 14, 1999 11:55 AM

ATOM RSS1 RSS2