| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 6627.1 | | SUTRA::16.36.3.236::Bats | Speeding, speeding, I'm always speeding | Mon Apr 28 1997 06:07 | 9 |
|
Don't know about the SWXCR, but on the Mylex it certainly does.
You'll the setting StorageWorks Management to be set to yes in
the SWXCR setup screen.
I'm quite sure that what the Mylex one does, is done exactly the
same by the SWXCR.
Pjotrr
|
| 6627.2 | RAID 0+1 redundancy | SUBSYS::TURCOTTE | fun stuff | Mon Apr 28 1997 22:37 | 14 |
| If you have an extra drive in your config set up as a hot spare,
and phsically remove a member of a RAID 0+1 set, the hot spare
will automatically kick in and replace the removed member of
the RAID set (assuming you have Fault Management enabled).
If you do not have an extra drive in your config as a hot spare,
and you remove a physical member of the RAID 0+1 set, the
logical RAID 0+1 set will continue to operate in degraded mode,
until you replace the failed member of the RAID 0+1 set, at
which time the automatic rebuild will take place - once the
rebuild is complete, the logical RAID 0+1 set will return to
optimal mode.
|
| 6627.3 | | KEIKI::WHITE | MIN(2�,FWIW) | Tue Apr 29 1997 18:25 | 9 |
|
Thanks,
All the info so far seems to contradict what the field told me
however it was a reliable source.
I didn't see why 0+1 would be any different from Raid 5 or Raid 1.
Bill
|
| 6627.4 | Probably a wrong policy set... | SSDEVO::RMCLEAN | | Wed Apr 30 1997 10:18 | 4 |
| There are a number of things that will cause it not to work.
Things like not having a large enough drive available or the
wrong replacement policy.
|
| 6627.5 | Hot Spare drive process works fine. | SUTRA::FRANCOIS | | Mon May 05 1997 11:57 | 17 |
| Re .0:
The host spare process is ok,just got an e-mail from a customer with
same problem as yours, the problem seems to be a system configuration
issue and not a raid controller one.
Hello Stephane,
Thanks for your different mail messages. Actually I think that I
found the source of all the Mylex problems: apparently the PCI busses
of
the test server produced strange Mylex board behaviours. This is the
second time that we have a problem like this. So, I mounted the Mylex
boards onto another server and all seems to work fine: SBY disks on
any
channel replace correctly "failing" disks on any channel, and a newly
inserted disk is correctly declared as the new SBY disk.
|