Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I would like to ask you to make me clear two things about SSDs.
1) Very often, when reading about the subject, there is an advice to leave some free space on the SSD.
I would like to ask, what does it mean?
How does one leave free space on a disk?
If I partition the disk, leaving unpartitioned area somewhere at the end, will the disk controller actually understand that?
And most importantly, does it matter at all for modern disks?
2) Can bad thing happen if fstrim is interrupted during operation (e.g. system shutdown while fstrim was scheduled to run by cron)?
Thanks in advance!
My SSDs are:
- Samsung SSD 850 EVO M.2 250GB, EMT21B6Q, max UDMA/133
- Samsung SSD 850 PRO 256GB, EXM02B6Q, max UDMA/133
I'll give you my opinions on this; others may have a different view.
Quote:
1) Very often, when reading about the subject, there is an advice to leave some free space on the SSD.
I would like to ask, what does it mean?
I believe this advice only applies to older SSDs. It refers to leaving some unallocated space(i.e. unpartitioned space) on the drive rather than partitioning the entire drive. This unallocated space can be used by the SSD firmware controller to increase the efficiency and life of the drive by using the unallocated space to perform certain functions peculiar to SSD drive maintenance, namely wear leveling, garbage collection and dealing with a technical phenomena known as write amplification:
The practice is known as "over-provisioning". I believe most modern SSDs, and certainly your Samsung SSDs, already come from the factory with hidden space not seen by your bios or operating system to be used for this purpose, i.e. they come from the factory over-provisioned. That was not always true of early SSDs. You can certainly leave some unallocated space on your SSDs if you want and it will be added to your already provided over-provisioned space and automatically used by your SSD firmware controller as needed. It may even be useful to do so in certain situations. In practice, I haven't found it necessary on recent SSD drives from Samsung or Intel. I don't have experience with other manufacturers.
Quote:
Can bad thing happen if fstrim is interrupted during operation (e.g. system shutdown while fstrim was scheduled to run by cron)?
As I understand it, fstrim just clears unused blocks from an SSD drive. If fstrim is interrupted, I would assume it just wouldn't complete the "trimming" of unused blocks and the next time fstrim was run those blocks would be detected and cleared.
I believe this advice only applies to older SSDs.
(..)
In practice, I haven't found it necessary on recent SSD drives from Samsung or Intel. I don't have experience with other manufacturers.
OK, I'm going to believe it too and won't bother any more. Thanks ;-)
Quote:
Originally Posted by kilgoretrout
As I understand it, fstrim just clears unused blocks from an SSD drive. If fstrim is interrupted, I would assume it just wouldn't complete the "trimming" of unused blocks and the next time fstrim was run those blocks would be detected and cleared.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.