RAID 5 URE Clarity Question
-
@scottalanmiller said in RAID 5 URE Clarity Question:
@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?
I see. I didn't understand that it was accumulative of each individual drive's URE rate.
Thanks for helping me to clear everything up.
-
@tim_g
Instead of rolling six sided dice:
During a rebuild after failed drive in a 6 drive RAID 5 array you have 5 dice with 10^14 sides each. One of the sides on each of these dice has a skull and crossbones. You roll all 5 of these dice thousands of times a second until the rebuild is complete. Just one of those dice on any roll during the operation required to rebuild needs to stop on skull and crossbones. Skull and crossbones wont come up right away, but given enough rolls it will. The number of dice rolls to rebuild is a function of array size and rebuild rate. Rebuild rate is the same for the RAID 5 set in question(whatever it is, is the same whether the array is 1TB or 1000TB). Higher array size = more chance of skull and crossbones. The relationship isnt linear, but the longer you dont land on skull and crossbones the higher the chance you will in the future.Now i am going to go design a DnD ruleset with 10^14 sided dice.
-
@momurda said in RAID 5 URE Clarity Question:
Now i am going to go design a DnD ruleset with 10^14 sided dice.
That's just mean!
@Tim_G I think you begin to understand why URE is so misunderstood.
-
Yeah I do see.
I experienced 2 of them in almost a single week. Though they were just for testing hardware and didn't contain any real data so no losses... They were very old drives too so it was expected after forcing a rebuild.
One was a 5TB raw RAID 5 (5x 1tb drives), the other was 1tb something raw, a bunch of old 15k 300gb SAS.
Actually the 5TB one got a URE, the other one, a 2nd drive failed, not a URE.
-
@tim_g said in RAID 5 URE Clarity Question:
Yeah I do see.
I experienced 2 of them in almost a single week. Though they were just for testing hardware and didn't contain any real data so no losses... They were very old drives too so it was expected after forcing a rebuild.
One was a 5TB raw RAID 5 (5x 1tb drives), the other was 1tb something raw, a bunch of old 15k 300gb SAS.
Actually the 5TB one got a URE, the other one, a 2nd drive failed, not a URE.
Actually it is unknown if UREs go up over time. Likely they do, but the statistics are only average rate and don't state when or what variables contribute to higher or lower rates.
