If you look after storage arrays you may have come to a situation like this.<\/p>\n
You have a disk array, you want to turn it off (for whatever reason, age, replacement, it smells of old cheddar.. whatever). \u00c2\u00a0Alas there is some customer still using a portion of it, you now need to wait for them to leave before you can decommision it.<\/p>\n
Well I have had an idea to ‘help’ them in their exodus from the shelf. \u00c2\u00a0Quite simply you enact storage Jenga. \u00c2\u00a0How does this work? \u00c2\u00a0easy, every day\/couple of days\/ weeks \u00c2\u00a0(depending on your desired timescale\/array size), you send a member of staff to site, once on site, that member of staff removes, physically a single disk from the array and leaves. \u00c2\u00a0Now the customer has a chance of surviving this, depending on your configuration and hot spares, but each disk removed increases their odds of goodbye \ud83d\ude42<\/p>\n
I imagine this will work with maximum excitement with RAID 10 arrays with a couple of hot spares, possibly pulling a disk JUST before the time it takes to rebuild the hotspare \ud83d\ude42<\/p>\n
Wonder if management will let me try it some time? Hmmmmm \ud83d\ude00<\/p>\n","protected":false},"excerpt":{"rendered":"
If you look after storage arrays you may have come to a situation like this. You have a disk array, you want to turn it off (for whatever reason, age, replacement, it smells of old cheddar.. whatever). \u00c2\u00a0Alas there is some customer still using a portion of it, you now need to wait for them … Continue reading Storage Jenga<\/span>