HP3000-L Archives

November 1996, 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:
Goetz Neumann <[log in to unmask]>
Reply To:
Date:
Sat, 16 Nov 1996 09:41:53 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Bill Lancaster wrote:
>
(lots of good stuff snipped)
> 2.  Better system resiliency.  Some disagree with this but most of the time,
> if you lose a volume which belongs to a user volume set the system won't go
> down.  Occasionally, it will, but generally it won't.

Just commenting about the 'resiliency' or 'high availability' aspect of
user volume sets:

1) Separating your data onto one (or preferably more) user volume set(s)
buys you a 'smaller unit of reload' in case of a disc failure where the
disc has to be replaced, i.e. recovery times are shorter.

2) Separating different applications onto different user volume sets
(assuming your system's user use more than one application) will mean
that the applications on the non-affected volume sets will at worst
be available directly after a reboot.

In general there is no way the operating system can handle all
possible hardware errors, so that it would not crash or hang.
It really depends on which disc operation is happening at the
time, and how the hardware error mainfests itself. Sometimes
you will just have a controller 'falling silent', sometimes
information critical to the OS will be corrupted, so the system
aborts.

Using Mirrored Disc/iX can really buy your more uptime for most
cases, but you should not expect 100% bulletproofness for there
are rare cases of undetectable corruptions.

Goetz.

ATOM RSS1 RSS2