« CLARiiON Write Cache | Main | Mapping the JFK Library Archive onto OAIS »

June 02, 2008

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Dave M

Great post Steve - very informative!

One sentence out of this article raises a question my teammates and I have been debating for some time...

"The cache would periodically be disabled and the BBU instructed to test itself."

So, on a CX3 series array, does write cache actually get disabled if/when a single SPS fails?

Thanks!

Steve Todd

Dave,

Great question, you correctly point out that my historical blogging goes back to the days of only one BBU, where today's product uses 2 SPS (standby power supplies).

FLARE's behavior in today's systems is to keep the cache enabled when one of the SPS faults or tests itself.

Cheers,
Steve

Hi Steve,

I don't know much about Clariion so this might be a silly question. The Clariion write cache is actually a different hardware cache or it is a part of Main Memory of the storage processors?
And when there is a power failure, the BBU shuts down everything else but the SPs and the first 5 disks, is that so?
Anand

Steve Todd

Anand,

The CLARiiON write cache is part of the main memory of the storage processors. So FLARE has to manage carving the memory between caching usage and FLARE's operational usage.

Regarding the BBU, as designed it needs to keep up the storage processors and 5 disks only. Keep in mind that today's CLARiiON use two SPS devices (standby power supplies) that operate in a similar fashion.

Steve

Andrés Suárez González

I suppose the 2 GB "module" for the CLARiiON dual storage processor is in more modern days than 1994, isn't it? Just curiosity for the real number...

Steve Todd

Hi Andres,
Yes you are correct, the latest CLARiiON to ship in August of 2008 has a maximum of 32GB of cache.
Regards,
Steve

The comments to this entry are closed.

by Steve Todd

Blog powered by Typepad

Employer

Disclaimer

  • The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by DELL Technologies and does not necessarily reflect the views and opinions of DELL Technologies nor does it constitute any official communication of DELL Technologies.