Subject: | |
From: | |
Reply To: | |
Date: | Wed, 17 Feb 1999 13:01:09 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Stan wrote:
>Doug writes:
>> The file that has caused the most trouble is PERFLOG.MPEXL.SYS. Under
normal
>> circumstances MPE won't mind if it isn't on ldev 1 because it isn't
required
>...
>
>It's not just that...many other files (particularly in @.DIAG.SYS) are
>not marked as "must be on ldev 1". The side effect is that if they migrate
>to another ldev, and then you do an "UPDATE", you've left semi-purged files
>in the label table ... which FSCHECK will report as problems later.
>
I agree with you. Those are problems, to be sure. As you say, they will give
you nasty errors during an update, and subsequently will be flagged by
FSCHECK. But under the right/wrong circumstances, PERFLOG can prevent your
system from booting.
Try this quick test (on a non production machine of course). Move
PERFLOG.MPEXL.SYS off of ldev 1 and then START NORECOVERY SINGLE-DISK. It
can't be done.
Doug.
Doug Werth Beechglen Development Inc.
[log in to unmask] Cincinnati, Ohio
The opinions expressed do not necessarily represent the views or opinions
of Beechglen Development. They might, but not necessarily. They represent
solely the opinions of the author.
|
|
|