On April 17, 2018 10:30:25 AM CDT, "D. Hugh Redelmeier via talk" <talk@gtalug.org> wrote:
| From: Russell via talk <talk@gtalug.org>
| >| From: Giles Orr via talk <talk@gtalug.org>
| >| I'm with Len - simplify if you can. Although Unlike him, I believe you | >| should have at least two (Linux) OS partitions - if one is messed up, you | >| can boot from the other to fix it. And I've also - more than once - | | I also follow this practice. In fact in my current build, I'm looking at | overprovisioning my SSD using small fencing stripes. This would so as to | be able to gain several spaces on the disk which I could format in an
| emergency. I can then recover a backup of the superblock and realign | things. In theory anyway.
"Overprovisioning" can mean many things, but it has a specific meaning in terms of SSD wear leveling.
Some system-visible space that is not being used can only be considered
overprovisioning (in the SSD wear leveling sense) if the drive's controller "knows" it is unused.
I guess that would mean that scattering unused space on an SSD between the partions, means the controller probably sees it as being used. I left chunks allocated at the ends of the drives as recommended. I was just wondering if my stripes would increase that wear level capability, as well as providing for emergency recovery space(s).
I haven't carefully read this but it might give answers on how to get empty bits between partitions into the free block pool of the SSD controller: <https://superuser.com/questions/308251/how-to-trim-discard-a-whole-ssd-partition-on-linux>
I'll check this out for sure. Thanks again.
--- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk
-- Russell