Home_greyopenFATE - openSUSE feature tracking > #321838
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Support TRIM/discard mode when installing to SSD

Feature state

openSUSE Distribution
Rejected Information


While installing Tumbleweed (and Leap 42.2) with an encrypted disk, there is no way to enable TRIM/discard mode the for the underlying SSD. I *can* specify the "discard" mount option in the expert partitioner mode, but I cannot add the necessary "--allow-discards" option to the call to "cryptsetup" anywhere. Only *after* booting the newly installed system it's possible to enable that feature, and even then I have to manually edit /etc/crypttab to do it.

User benefit:

TRIM mode allows modern SSDs to operate faster than they can without it.

There are security implications when combined with LUKS encryption, but having that ability as an optional feature sure is desirable (and many other distributions support it, too).


icons/user_comment.png M. P. wrote: (8 months ago)

This behaviour is afaik intentional - enabling discard as mount option/or with luks can lead to premature degradation of many ssd devices - on other hand fstrim from util linux has service/timer which will trigger it periodically which is in most cases sufficient and safe.

icons/user_comment.png P. S. wrote: (8 months ago)

Actually, it's the other way round. TRIM was invented to *prevent* SSD degradation and to improve both longevity and performance of SSD drives, i.e. by combating Write Amplification. https://en.wikipedia.org/wiki/Write_amplification has some details. Running fstrim via cron alleviates these issues to some degree, but it's certainly not the same thing as using TRIM continuously. It feels really weird that openSUSE does not take advantage of these features which have been around (and are standard practice in other distributions) for several years now.

icons/user_comment.png M. P. wrote: (8 months ago)

Intention and implementation sadly differ - there are plenty of ssd drives with faulty trim implementations see [1][2] and it is often recommended against enabling this unless one is sure that his drive is not among faulty ones.

1. https://forums.freebsd.org/threads/56951/#post-328912
2. https://wiki.debian.org/SSDOptimization

icons/user_comment.png P. S. wrote: (8 months ago)

Yes, I am sure SSDs with broken firmware exist. That is a compelling reason to not enable TRIM features unconditionally. Instead, users should have the option to enable use of TRIM if they want to. The reason I created this FATE entry is because openSUSE's installer does not allow its users to do that.

icons/user_comment.png M. P. wrote: (8 months ago)

Afaik potentially dangerous options were intentionally ommited from installer, leaving advanced users with necessity to use other means to achieve what they wanted - but we can of course re-open this fate - maybe it will become more interesting to YaST team in future and they will want to implement this (probably with necessary warning)

icons/user_comment.png O. K. wrote: (8 months ago)

While I fully appreciate the effort grooming the existing fate issues I think we should not overdo it and reject feature requests which at least some people say are valid even though we do not immediately find someone who can implement it.

icons/user_comment.png M. P. wrote: (8 months ago)

Well reopening fate request is not much difficult ...

Last change: 8 months ago
Score: 3
  • Negative: 0
  • Neutral: 0
  • Positive: 3
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint