Theo,
If you keep some amount like 10% of the SSD zeroed then the
controller can use those blocks to improve the wear lifetime
('over provisioning').
Do you mean unpartitioned, or would something special (zeroed?) be needed ?
And thanks for the suggestion.
Regards,
Rudy Wieser
Theo,
If you keep some amount like 10% of the SSD zeroed then the
controller can use those blocks to improve the wear lifetime
('over provisioning').
Do you mean unpartitioned, or would something special (zeroed?) be needed ?
Theo,
'Empty'. When you delete a file, typically filesystems tell the
device that the blocks are no longer used
Ah, you mean I should never fully use the whole partition ("Used
space" vs "Free space"). With 128GB to work with I'm not going to
worry about that. :-)
If you zero blocks, the SSD can also decide they're 'empty'.
I don't understand : when a block is not part of any file chain than its unused. The wear-leveling process could commandeer such blocks at any
time - even though that could twart a later "undelete" attempt.
If you keep some amount like 10% of the SSD zeroed then the
controller can use those blocks to improve the wear lifetime
('over provisioning').
'Empty'. When you delete a file, typically filesystems tell the
device that the blocks are no longer used
If you zero blocks, the SSD can also decide they're 'empty'.
If you leave parts unpartitioned but still containing data from
the last time it was used, the SSD is still contractually obliged
to keep the data in case you need it another time
but also zeroing the SSD and then leaving 10% (or whatever)
unpartitioned works too.
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 122 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 07:15:16 |
| Calls: | 9,714 |
| Calls today: | 4 |
| Files: | 9,589 |
| D/L today: |
401 files (428M bytes) |
| Messages: | 435,275 |
| Posted today: | 6 |