RAID 5 URE Clarity Question
-
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
So isn't drive D only needed for the 400GB it contains of drive E to help rebuild it?
No, D doesn't contain ANYTHING of drive E. That's likely the root of confusion. At no point in parity RAID does any drive contain the contents of any other drive. That's mirroring, and mirroring doesn't have this risk at all.
That's not how I mean it... it contains 400GB of parity data that is used to help reconstruct the data in drive E, doesn't it?
-
But not matter what, there's a good 400GB of crap on drive D that is needed to help rebuild the data that was on drive E...
-
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
So isn't drive D only needed for the 400GB it contains of drive E to help rebuild it?
No, D doesn't contain ANYTHING of drive E. That's likely the root of confusion. At no point in parity RAID does any drive contain the contents of any other drive. That's mirroring, and mirroring doesn't have this risk at all.
That's not how I mean it... it contains 400GB of parity data that is used to help reconstruct the data in drive E, doesn't it?
No, it contains 2TB of parity data, every block of which is necessary for reconstructing the lost drive(s).
-
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
So isn't drive D only needed for the 400GB it contains of drive E to help rebuild it?
No, D doesn't contain ANYTHING of drive E. That's likely the root of confusion. At no point in parity RAID does any drive contain the contents of any other drive. That's mirroring, and mirroring doesn't have this risk at all.
That's not how I mean it... it contains 400GB of parity data that is used to help reconstruct the data in drive E, doesn't it?
No, it contains 2TB of parity data, every block of which is necessary for reconstructing the lost drive(s).
Oh I see... I had it wrong the whole time.
-
@tim_g said in RAID 5 URE Clarity Question:
But not matter what, there's a good 400GB of crap on drive D that is needed to help rebuild the data that was on drive E...
No, parity RAID is like a single file, when it corrupts, it is lost. Doesn't matter how many good blocks there are.
-
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
But not matter what, there's a good 400GB of crap on drive D that is needed to help rebuild the data that was on drive E...
No, parity RAID is like a single file, when it corrupts, it is lost. Doesn't matter how many good blocks there are.
So then it means the entire 2TB of EVERY drive needs to be READ to reconstruct the 2TB that was on the bad drive.
-
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
So isn't drive D only needed for the 400GB it contains of drive E to help rebuild it?
No, D doesn't contain ANYTHING of drive E. That's likely the root of confusion. At no point in parity RAID does any drive contain the contents of any other drive. That's mirroring, and mirroring doesn't have this risk at all.
That's not how I mean it... it contains 400GB of parity data that is used to help reconstruct the data in drive E, doesn't it?
No, it contains 2TB of parity data, every block of which is necessary for reconstructing the lost drive(s).
Oh I see... I had it wrong the whole time.
I figured that out
So it is 2TB, from every working drive in the array (4), for 8TB total. Which gives us somewhere around a 60% chance of hitting a URE. That's because 12T is an average, not a guarantee. If it was exactly every 12TB, it would be 67% chance of loss. -
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
But not matter what, there's a good 400GB of crap on drive D that is needed to help rebuild the data that was on drive E...
No, parity RAID is like a single file, when it corrupts, it is lost. Doesn't matter how many good blocks there are.
So then it means the entire 2TB of EVERY drive needs to be READ to reconstruct the 2TB that was on the bad drive.
Correct
-
@scottalanmiller said in RAID 5 URE Clarity Question:
So it is 2TB, from every working drive in the array (4), for 8TB total,
to avoid confusion, do you mean (5), for 10TB total? Because there's 6 total, one went bad, 5 working ones left?
-
@scottalanmiller said in RAID 5 URE Clarity Question:
t you buy, because that's what sets the failure rate. Obviously it is physical drives that fail, so it is the quality of the drives you
you guys are bouncing between RAID 5 and 6 conversations..
-
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
So it is 2TB, from every working drive in the array (4),
to avoid confusion, do you mean (5), for 10TB total? Because there's 6 total, one went bad, 5 working ones left?
No, because URE risk only matters when two drives are lost in RAID 6. If you had five drives, you have no URE risk.
-
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
So it is 2TB, from every working drive in the array (4),
to avoid confusion, do you mean (5), for 10TB total? Because there's 6 total, one went bad, 5 working ones left?
No, because URE risk only matters when two drives are lost in RAID 6. If you had five drives, you have no URE risk.
I'm talking about a 6x 2TB drives in a RAID 5. One of those drives goes bad, so you hot-swap it out with a good one and the rebuilding starts. At this point, URE matters because if a 2nd drive dies before the rebuild is complete, game over.
I'm not asking or saying anything at all about RAID 6.
-
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
So it is 2TB, from every working drive in the array (4),
to avoid confusion, do you mean (5), for 10TB total? Because there's 6 total, one went bad, 5 working ones left?
No, because URE risk only matters when two drives are lost in RAID 6. If you had five drives, you have no URE risk.
I'm talking about a 6x 2TB drives in a RAID 5. One of those drives goes bad, so you hot-swap it out with a good one and the rebuilding starts.
I'm not asking or saying anything at all about RAID 6.
Whoops.
In that case you need 500% of a single drive. So the failure domain is 10TB, not 8TB. Sorry, got confused. You need the full capacity of all five remaining drives to restore the one that has been lost.
-
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
So it is 2TB, from every working drive in the array (4),
to avoid confusion, do you mean (5), for 10TB total? Because there's 6 total, one went bad, 5 working ones left?
No, because URE risk only matters when two drives are lost in RAID 6. If you had five drives, you have no URE risk.
I'm talking about a 6x 2TB drives in a RAID 5. One of those drives goes bad, so you hot-swap it out with a good one and the rebuilding starts.
I'm not asking or saying anything at all about RAID 6.
Whoops.
In that case you need 500% of a single drive. So the failure domain is 10TB, not 8TB. Sorry, got confused. You need the full capacity of all five remaining drives to restore the one that has been lost.
Okay, that's what I thought and wanted to make sure or i'd be confused again.
-
Sorry about the RAID 6 confusion. Everything referencing 8TB or 400% was me thinking this was six drives in RAID 6 and losing two, instead of six disks in RAID 5 losing one.
-
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
So isn't drive D only needed for the 400GB it contains of drive E to help rebuild it?
No, D doesn't contain ANYTHING of drive E. That's likely the root of confusion. At no point in parity RAID does any drive contain the contents of any other drive. That's mirroring, and mirroring doesn't have this risk at all.
That's not how I mean it... it contains 400GB of parity data that is used to help reconstruct the data in drive E, doesn't it?
No, it contains 2TB of parity data, every block of which is necessary for reconstructing the lost drive(s).
Oh I see... I had it wrong the whole time.
I figured that out
So it is 2TB, from every working drive in the array (4), for 8TB total. Which gives us somewhere around a 60% chance of hitting a URE. That's because 12T is an average, not a guarantee. If it was exactly every 12TB, it would be 67% chance of loss.Okay yes. But a URE happens on a single drive. And the rate of a URE happening on a single drive is 10^14. 2TB of reads is only 16.6% of 12TB. So I still don't see where you get your 60-67% chance from.
-
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
So isn't drive D only needed for the 400GB it contains of drive E to help rebuild it?
No, D doesn't contain ANYTHING of drive E. That's likely the root of confusion. At no point in parity RAID does any drive contain the contents of any other drive. That's mirroring, and mirroring doesn't have this risk at all.
That's not how I mean it... it contains 400GB of parity data that is used to help reconstruct the data in drive E, doesn't it?
No, it contains 2TB of parity data, every block of which is necessary for reconstructing the lost drive(s).
Oh I see... I had it wrong the whole time.
I figured that out
So it is 2TB, from every working drive in the array (4), for 8TB total. Which gives us somewhere around a 60% chance of hitting a URE. That's because 12T is an average, not a guarantee. If it was exactly every 12TB, it would be 67% chance of loss.Okay yes. But a URE happens on a single drive. And the rate of a URE happening on a single drive is 10^14. 2TB of reads is only 16.6% of 12TB. So I still don't see where you get your 60-67% chance from.
Or I mean 2TB is only 20% of 10TB... so not seeing the 60-67% you come up with.
-
@tim_g said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
So isn't drive D only needed for the 400GB it contains of drive E to help rebuild it?
No, D doesn't contain ANYTHING of drive E. That's likely the root of confusion. At no point in parity RAID does any drive contain the contents of any other drive. That's mirroring, and mirroring doesn't have this risk at all.
That's not how I mean it... it contains 400GB of parity data that is used to help reconstruct the data in drive E, doesn't it?
No, it contains 2TB of parity data, every block of which is necessary for reconstructing the lost drive(s).
Oh I see... I had it wrong the whole time.
I figured that out
So it is 2TB, from every working drive in the array (4), for 8TB total. Which gives us somewhere around a 60% chance of hitting a URE. That's because 12T is an average, not a guarantee. If it was exactly every 12TB, it would be 67% chance of loss.Okay yes. But a URE happens on a single drive. And the rate of a URE happening on a single drive is 10^14. 2TB of reads is only 16.6% of 12TB. So I still don't see where you get your 60-67% chance from.
Or I mean 2TB is only 20% of 10TB... so not seeing the 60-67% you come up with.
Because it's cumulative. It's X% per drive you're reading from.
Going back to the 6 TB of data in the 6 disk array, one drive dies, the remaining 5 drives each have a 10%, so youhave 5 * 10% = 50% total chance.
-
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
So isn't drive D only needed for the 400GB it contains of drive E to help rebuild it?
No, D doesn't contain ANYTHING of drive E. That's likely the root of confusion. At no point in parity RAID does any drive contain the contents of any other drive. That's mirroring, and mirroring doesn't have this risk at all.
That's not how I mean it... it contains 400GB of parity data that is used to help reconstruct the data in drive E, doesn't it?
No, it contains 2TB of parity data, every block of which is necessary for reconstructing the lost drive(s).
Oh I see... I had it wrong the whole time.
I figured that out
So it is 2TB, from every working drive in the array (4), for 8TB total. Which gives us somewhere around a 60% chance of hitting a URE. That's because 12T is an average, not a guarantee. If it was exactly every 12TB, it would be 67% chance of loss.Okay yes. But a URE happens on a single drive. And the rate of a URE happening on a single drive is 10^14. 2TB of reads is only 16.6% of 12TB. So I still don't see where you get your 60-67% chance from.
Why do you keep mentioning single drives when the risk is all the drives together? Yes, the actual URE might occur on any one of the drives, but each has an equal risk in any give operation. So the risk domain is 10TB, or 60%. I can't figure out why you keep mentioning a single drive and tying that to the risk domain, there are more than one drive here, all of them are 100% necessary.
-
@tim_g said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
@scottalanmiller said in RAID 5 URE Clarity Question:
@tim_g said in RAID 5 URE Clarity Question:
So isn't drive D only needed for the 400GB it contains of drive E to help rebuild it?
No, D doesn't contain ANYTHING of drive E. That's likely the root of confusion. At no point in parity RAID does any drive contain the contents of any other drive. That's mirroring, and mirroring doesn't have this risk at all.
That's not how I mean it... it contains 400GB of parity data that is used to help reconstruct the data in drive E, doesn't it?
No, it contains 2TB of parity data, every block of which is necessary for reconstructing the lost drive(s).
Oh I see... I had it wrong the whole time.
I figured that out
So it is 2TB, from every working drive in the array (4), for 8TB total. Which gives us somewhere around a 60% chance of hitting a URE. That's because 12T is an average, not a guarantee. If it was exactly every 12TB, it would be 67% chance of loss.Okay yes. But a URE happens on a single drive. And the rate of a URE happening on a single drive is 10^14. 2TB of reads is only 16.6% of 12TB. So I still don't see where you get your 60-67% chance from.
Or I mean 2TB is only 20% of 10TB... so not seeing the 60-67% you come up with.
Right, and 20% x 5 is?
