Calculating available disk space in a RAID-5 set

Calculating available disk space in a RAID-5 set

I'm trying to find out how to calculate how much disk space will be available from five 36 GB disks using RAID-5. Can you help me out?

    Requires Free Membership to View

    When you register for SearchStorage.com, you’ll also receive targeted emails from my team of award-winning editorial writers. Our goal is to keep you informed on the hottest topics, the latest news and the biggest challenges you face as a storage professional today.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchStorage.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchStorage.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

 

Five 36 GB drives in a RAID-5 configuration yields 144 GB of useable space. I figured this out using a RAID calculator from ibeast that can be found at http://www.ibeast.com/content/tools/RaidCalc/RaidCalc.asp

In addition to providing the simple RAID calculations, the tool also provides information on the various RAID configurations. For RAID-5, the tool provides:

RAID level 5 data striping with distributed parity definition
----------------------------------------------
Data is striped across a group of disk drives with distributed parity. Parity information is written to a different disk in the array for each stripe.

Redundancy
----------------------------------------------
Parity is distributed across the disks in the array. Data is regenerated in the event of a drive failure.

Performance
----------------------------------------------
High performance in small record, multiprocessing environments because there is no contention for the parity disk and read and write operations can be overlapped. No write bottlenecks as with RAID-4.

Drawbacks
----------------------------------------------
Distributed parity causes overhead on write operations. There is also overhead created when data is changed, because parity information must be located and then recalculated.

 

This was first published in January 2005