SSD as a hard drive: how much should be left unallocated?

Question

Solid State Drives

I heard that for SSD hard drives, a few gigabytes should be left unallocated so that the controller replaces failed sectors with them during operation.

Is it true? And how much does it cost to leave in this case?

My SSD: Intel 320 series 80 GB.

PS And in general, is it worth worrying about a limited number of rewriting cycles, or are these already problems from the distant past?

Answer 1

Any modern SSD has a redundant reserved memory area, just designed to wear out over time. So there is no point in bothering with manual reservations at all.
But as for wear in general, for the time being, with a decrease in the technical process, the resource of the cells decreases, but this is compensated by the increased amount of memory.

Answer 2

and here again I burst into a post about hardware, advising you not to listen to the nonsense of previous speakers =)
1. limiting rewriting cycles is the most real thing.
2. The controller is able to use the unallocated area for remap together with the internal reserve.
leave as much as you feel sorry for, estimate how much you will definitely have enough for the system for the entire life of the drive, leave the rest unallocated. 64 gigabytes, it seems to me, is over the top, leaving the rest under remap will be reasonable (10-20 percent).
By the way, have you already bought a 320ku? Are you afraid of a bug in the firmware? if you haven’t taken it yet, I would recommend waiting for a fix or taking something more different.

Answer 3

Not to mark - it makes no sense.
It is enough to leave about 25% of the space free.
The rest will happen automatically.

Answer 4

С циклами перезаписи, не уверен, что такой проблемы уже не существует, поэтому немного задумываться об этом стоит, но в случае когда активно SSD не используется под КЭШ/Своп/временные файлы думаю можно первое время(год два) спать спокойно.
А вот со свободными гигабайтами информация сильно попахивает бредом. Объясню почему мне так кажется. Винчестер(жесткий диск, не важно как реализованный) содержит в себе только информацию в ноликах и единичках. О том что эти нолики и единички являются томом файловой системы какого то типа, он не знает и поэтому спит спокойно. Раз он не знает про файловые системы, то и управлять ими соответственно не может. Соответственно сам жесткий диск ну никак этого не сделает, хотя ВОЗМОЖНО есть программная утилита, которая позволяет в SSD такое вот тройное сальто с приземлением на голову.

Answer 5

Pieces of iron for us, not we for pieces of iron. Make an automatic backup and do not be afraid of anything. When (and if) it dies, calmly buy a new disk and restore the backup.

Answer 6

Personally, I reduced the swap (the minimum size is 100MB, and the maximum size is 512) because of space, and not because of fear of overwriting. I didn’t leave the unallocated either, and I didn’t hear much about it, on forums in topics about SSD, usually if people ask “did anyone leave unallocated space on SSD?”, Then they get negative answers.
Here on the M4 64GB and a few more (next to similar topics) of 250-500TB were recorded and are still alive. Intel of the previous models, like 150-200 TB, died there.
By the way, in my opinion, the phrase "SSD hard drive" is incorrect :) HDD - Hard Disk Drive, hard drive. SSD - Solid State Drive.

Answer 7

The trick is that rewriting cycles on modern screws will last for 3-5 years ...
I have not read anywhere about the death of an SSD from abrasion, everywhere on the Internet they write about the death of the controller. The process of disc wear is long and easy to monitor. But the controller dies suddenly and irrevocably ...
In general, I don’t see any point in paying close attention to abrasion, one fig screw will die from the death of the controller ...