RAID Link Blast

scottalanmiller

Most (all?) RAID calculators completely ignore the most significant risks (UREs on parity rebuild, availability impact during rebuild, etc.) and focus only on "background noise" risks so are worse than useless, they are actively misleading. They might be useful for RAID 1 risk calculation but even then have to take on huge assumptions like hot swap instant kick in to eliminate other factors like time to source a replacement drive (which they should, but it remains complex as that is a factor.) The calculators are typically made based on 1990s risk assumptions that are essentially irrelevant today so they are very bad.

scottalanmiller

Even for pure disk failures, to really get good numbers you have to know the exact drive and have a large scale study of that drive available. You need the failure curve and to understand the risk for a given period of time. Risks skyrocket in years three through five, for example, from disk failure which is almost unheard of from six to twenty four months.

thanksajdotcom

Thanks for the links for reference @scottalanmiller!

RoguePacket

@scottalanmiller Good bits.

Considering the "storage engineer" role continues to be an emerging one, better barometers do need to exist. If not number, perhaps one with adjective associations—"are you nuts??", "hmm, not bad", "can do that if you don't mind losing everything", etc.

Kind of saying it jokingly, but there is a need.

scottalanmiller

Just added the Comparing RAID 10 and RAID 01 link to the list.

technobabble

I have read almost all of these. Do you have any IOPS per RAID stuff?

scottalanmiller

Nothing on IOPS. That'll be a good topic for a future one, thanks!

technobabble

Your welcome. I found a site a couple years ago with an IOPS calculator per RAID type.

scottalanmiller

Just added the RAID 100 link to the list.

technobabble

@technobabble said:

Your welcome. I found a site a couple years ago with an IOPS calculator per RAID type.

Here is the IOPS calculator I was talking about.

scottalanmiller

@technobabble said:

@technobabble said:

Your welcome. I found a site a couple years ago with an IOPS calculator per RAID type.

Here is the IOPS calculator I was talking about.

That's the one that I often use.

Carnival Boy

Do SMB people still have RAID arguments? I just figured everyone was RAID 10 now.

I had a quote for a new ERP system last week and in the vendor proposal under recommendations for SQL server they've written "at least 300Gb of disk space in RAID 5". I was bit WTF, haven't we moved on from specifying RAID levels?

This is an ERP vendor, although they do IT support as well. I've no idea where they came up with the 300Gb figure from either. Disks are so cheap these days and you can get 600GB SFF disks so lack of storage seems unlikely to be a problem in a typical SMB.

scottalanmiller

@Carnival-Boy said:

Do SMB people still have RAID arguments? I just figured everyone was RAID 10 now.

Every few hours. RAID 6 still plays a huge role in SMB needs too. Far under 50%, but way more than 1%. I'd guess somewhere around 15-20% but that's scientific at all. RAID 10 and RAID 6 make up the vast majority of all SMB storage recommendations, though (assuming that RAID 1 is a subset of RAID 10 and RAID 100 is a super set that we ignore.)

scottalanmiller

@Carnival-Boy said:

I had a quote for a new ERP system last week and in the vendor proposal under recommendations for SQL server they've written "at least 300Gb of disk space in RAID 5". I was bit WTF, haven't we moved on from specifying RAID levels?

Especially from specifying the worst possible RAID level. Even in the 1990s RAID 5 was a "compromise" level. It should never be specified as a requirement, only possibly a minimum. In this case, the wording is confusing. Maybe they meant RAID 5 (or better) which is okay potentially. But requiring RAID 5 period, is bad. All depends on how they meant it to read.