Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Overprotective, friendly and very very bad

Status
Not open for further replies.

ozihcs

IS-IT--Management
Jan 10, 2005
12
0
0
NO
.. well pardon the inflammatory subject, but currently I'm a bit annoyed because I've just realized that my entire production farm will be running in slow motion for the entire weekend because I have a faulted disk being replaced by hotspare.

I can understand the rationale behind forcibly disabling the write cache if there are faults, but in this case the protective measures are by themselves much more catastrophic than the drive failure which caused it. And to top it off there doesn't even seem to be any way to reenable the cache and accept the risk of data loss if another 2 drives should fail.


Oh well. I'm sure that it seemed like a very good idea at the time..
 
Write cache on a Clariion should only be disabled if your SPS battery is low or down and/or you have an SP down. A failed drive should not cause write cache to disable.
 
in addition to the above, the rebuild to the hotspare shouldn't take long so it should be back to normal performance within an hour tops (depending on the rebuild priority set for the raid group with the failed) if your cache is disabled it may be wise to check the SP event logs and see if anything else has happened i.e SP reboot.
 
Still waiting for my replacement drive, but I've discovered why the cache was disabled. If the HA Cache Vault option is enabled on the storage array (default), any faulted disk will cause a disable of the write cache. With this option off, the cache will stay enabled. Unfortunately, once the cache has been disabled, clearing the HA Cache Vault tick won't allow the write cache to enable - only a replacement of the failed drive will fix it. Safe I guess, but I may choose to disable it since the lack of a write cache in our case is far worse than the lack of a free hotspare drive.
 
As ozihcs noted, CLARiiONs require that the vault be present and accounted for.

If you have only 10 drives, well, any failure of the first 9 will kill your write cache.

If you lost a drive on a second DAE, then it wouldn't affect it.

I was reminded of this when I played around with drive rebuilding on my 4500 (I run one at home)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top