I could not find anything on Intel's site regarding the stock overprovisioning for each SSD. I did find this procedure on Infortrend to check the existing OP and change the allocation amount. http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CCYQFjAA&url=http%3A%2F%2Fwww.infortrend.com%2FImageLoader%2FLoadDoc%2F435&ei=7lQOU-DLBYWN2gW5p4GACQ&usg=AFQjCNGBpet0DIVCeHIWvPtQfMabrAQLFg&bvm=bv.61965928,d.b2I
I haven't had a chance to test this yet, but will post results when I can. If we could get some feedback from an Intel engineer, that would be better.
1 of 1 people found this helpful
Our drives are overprovisioned from the factory, but that space is not visible to the user.
Unpartitioned space is not used by the SSD to keep performance up (it’s not the same as the space set aside for overprovisioning). It's left alone in case the user wants to use it.
Following the instructions at the document you shared will increase the amount of overprovisioning, but the trade-off is that you will have less usable space for storage.
Thanks for the quick reply Joe!
Yes, after digging deeper it seems that the enterprise grade SSDs have a large amount of OP, which is great for performance and longevity. From what I've gathered it's between 33 and 60%. I was just curious what the factory amount is set to, or what Intel engineers consider best practice for enterprise environments.
Thanks again for your input!
Here's the direct link to that doc:
It mentions Linux' hdparm, but provides no guidance. This article details how to read & modify the Host Protected Area (HPA), using hdparm:
My original question was whether HPA was an effective means of over-provisioning on Intel SSDs. Of particular interest to me are the SSD 520 and SSD 535. While the later posts in this thread suggest the answer is "yes", I'd appreciate it if someone could confirm.
BTW, I assume you need to Secure Erase (or delete everything and TRIM), before doing this. Also, don't be surprised if you need to create a new partition table, as parted aborted when it tried to read the GPT left on the drive from before.