ssd Does SSD custom over-provisioning persist between operating systems?

[Shutset]

Does anyone know how to control the overprovisioning on SSDs on Linux or BSD?

So far, I've only managed to increase the overprovisioning of my Samsung NVMe drive, using Samsung Magician

but I really want to be able to do the same for my SSD's in my Linux computers.

 

If I can't do it from within Linux or BSD, could the new overprovisioning settings I set in Windows

be carried over to other operating systems?

 

Let's say I increase the overprovisioning of an SSD to 50% on Windows, using Samsung Magician,

then remove Windows and install a Linux distro on it. Will it still have half of its storage capacity overprovisioned?

 

Thanks.

[igormp]

4 minutes ago, Shutset said:

Will it still have half of its storage capacity overprovisioned?

No, you'd need to partition the disk yourself and leave 50% of it free. But why would you do that? The built-in overprovisioning is more than enough for years of usage.

[Electronics Wizardy]

You really don't need to worry about writes killing a modern drive. They can take a lot more than any normal user could put on them(Im killing 8 ssds for a test, and they have lastest >6 months of continous writes already, and this is a dramless tlc drive).

 

The samgsung software just shrinks the partitions, nothing special. Have free space on your disk will do the same thing as trim is used.

[Shutset]

1 hour ago, igormp said:

No, you'd need to partition the disk yourself and leave 50% of it free. But why would you do that? The built-in overprovisioning is more than enough for years of usage.

Just 10% of the capacity?

[igormp]

5 minutes ago, Shutset said:

Just 10% of the capacity?

Yes, and that's transparent to you. Even if you fill the drive, those 10% extra will still exist behind the curtains.

[kokosnh]

There are like 3 things that you could name overprovisioning
1) Spear NAND cells. 
2) The cut RAW to User NAND Capacity by the SSD controller, like 2048GB to 2000GB, that NAND is used for TRIM and so on. 
3) The unformatted space, that you just leave on your initialized SSD, beside the formatted partitions, that NAND is used for TRIM and so on. 

But the SSD will still use the free formatted space left on the SSD partition, for TRIM, pSLC bufor (well it depends) and wear leveling. 

It's all depend on why are you wanting to do it... What's the purpose?

 

[Shutset]

1 hour ago, kokosnh said:

It's all depend on why are you wanting to do it... What's the purpose?

Simply to extend my SSD's lifespan as much as possible.

[kokosnh]

Then just don't fill it up past 80%, it won't matter much, if it's just empty space on partition, or unformatted space beside the formatted partitions. 
Today good SSD have strong error correction algorithms, good wear leveling, and some have data refresh function to refresh the old data, before it's gone...
Just don't leave your SSD without power for months (especially somwere hot), don't cool the NAND when its operating, and don't buy cheap QLC or TLC drives.  Buy good TLC, or MLC SSD, or optane     

Just have good PSU with low ripple, it's rather hard to kill the NAND in good TLC SSD. It's more likely that the controller will just die.
do you have lots of writes to the SSD?    
If it's important server, that just have RAID 1 from the identical SSD.