Comments on: SSD configuration for openSUSE Blogs and Ramblings of the openSUSE Members Fri, 06 Mar 2020 17:50:09 +0000 hourly 1 By: Barry Weaver Sat, 07 Mar 2015 23:25:16 +0000 Efstathios:

Thank you for the great article. I would like to point out an alternative mechanism to schedule fstrim (#6). The util-linux package has a systemd timer in it for fstrim [1]. It is relatively new, so it may not be an option in all versions but it is available in openSUSE 13.2.

All that is required for for the timer be enabled and active with systemctl is:
$ systemctl enable fstrim.timer
$ systemctl start fstrim.timer


By: Bruno Friedmann Thu, 12 Feb 2015 13:55:50 +0000 First keeping a small swap partition is still recommended for performance usage.
relatime is still a good choice as explained in previous comment
Removing swap partition kill automatically the hibernation possibility.
Your log in tmpfs good be and idea, but if there’s a problem it will be hard to diagnose whatever.

And you forget to add the most advisable idea : check and apply any mfg recommended firmware!
Mfg have fixed numerous crash or prematurely dying ssd during the last few years.

Before buying an ssd, try to discover (often hidden informations) the limit of write the model propose. You could be surpized 🙂 Some are good, other really bad. The last Samsung 850 1To for example wouldn’t survive 1.5 year at the pace I use my laptop… Crucial M550 or older Corsair GT3 doesn’t seems to suffer….

My last advise is also the following, if you use encryption luks over your ssd, by default there’s no trim/discard available by default on openSUSE. Be it a good idea for security, cause empty blocks will never get aligned, I’m still not sure it is a good or wise default for ssd.

In my case, every 1.5 years I totally secure erase the ssd, and restore my system on them afterwards.

By: Frank Mon, 09 Feb 2015 17:10:09 +0000 Hello:

I think that some applications need to take into account the changes that occur in their files.

If it gets ‘noatime’ changes in the inode is not going to produce, but if we put realtime, change only if the file is changed, if it is not, It would behave like noatime ; i think that for applications that need to be on the basis of the dates and the access time of files, i think that realtime is a better option.

Even i do not know many of the improvements that can bring btrfs in configurations of SSD drives; but I think that these are some, To be able to rid some of the changes that are made in EXT4; by now not know them, but my fstab configuration for an SSD in BTRFS, that used for tests with VirtualBox is this:

UUID d8c57867-8bad-41DB-85CF-219b41Eddd22 /home/frank/VBox_ssd btrfs discard realtime ssd 0 0

Thank you for your article .

I look forward to reading more about this topic.


PD. Sorry if my English is not correct.

By: ali Mon, 09 Feb 2015 14:08:11 +0000 and after all to care of ssd you can move it from your system
or remove your os
or turn down your ssytem forever
and be sure your ssd never be die 😉
disable hibernate not good…
disable cahce not good…
only make cache lower and slower…
vm.swappiness=1 is good for example