Comment 2 for bug 1332720

Revision history for this message
pinumbernumber (pinumbernumber) wrote : Re: [Bug 1332720] Re: Mint does not accommodate SSDs (no TRIM)

Okay, thanks for that. That entirely invalidates my report, although I do
now wonder if "discard" is still slower with current kernel versions and
post-2011 SSDs. I can't find updated info on the matter.

Keeping the scheduled fstrim is clearly the safer option though. Sorry for
wasting time
On 20 Jun 2014 23:00, "Michael Webster" <email address hidden> wrote:

> It's not well-documented, but have a look at this, the contents of your
> /etc/cron.weekly/fstrim:
>
> #!/bin/sh
> # call fstrim-all to trim all mounted file systems which support it
> set -e
>
> # This only runs on Intel and Samsung SSDs by default, as some SSDs with
> faulty
> # firmware may encounter data loss problems when running fstrim under high
> I/O
> # load (e. g. https://launchpad.net/bugs/1259829). You can append the
> # --no-model-check option here to disable the vendor check and run fstrim
> on
> # all SSD drives.
> exec fstrim-all
>
> If you have a Samsung or Intel brand SSD, it's already there, and runs
> on a schedule, otherwise (and if you're sure your drive is capable), you
> have to add the --no-model-check flag to this.
>
> This article explains a bit why the discard flag isn't used:
> http://www.howtogeek.com/176978/ubuntu-doesnt-trim-ssds-by-default-why-
> not-and-how-to-enable-it-yourself/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1332720
>
> Title:
> Mint does not accommodate SSDs (no TRIM)
>
> Status in The Linux Mint Distribution:
> New
>
> Bug description:
> I'm running Linux Mint 17 Cinnamon x64 on a system including a Samsung
> 840 EVO SSD.
>
> What you did for the problem to happen, and how to reproduce it:
> * Install mint on an SSD.
> * Observe that the "discard" flag is not used when mounting the volume,
> meaning online TRIM is not being used.
> * I can't find any scheduled fstrim either, although I'm not used to
> upstart so I may be missing something. In any case, mounting with "discard"
> is a preferable solution for modern SSDs.
>
> What happened:
> * TRIM is not utilised.
>
> What you expected to happen instead:
> * TRIM should be utilised by having the volume mounted with the
> "discard" flag. (Or possibly with a scheduled fstrim, as I believe Ubuntu
> does, but this is probably not optimal except on old and/or poor quality
> SSDs which are slow to process online TRIM. On modern SSDs, online trim
> ("discard") is preferred.)
>
> If the problem happened once, sometimes, or always:
> * Always.
>
> ====
>
> Manual workarounds:
> * Open /etc/fstab as root, add "discard" flag, reboot.
>
> ====
>
> Other:
> * Although some SSDs (Intel) will work okay without TRIM, others
> (Samsung) require it or will quickly degrade in performance until it is
> applied.
> * On such systems (which are likely common since the 840 and its EVO
> successor are bestselling SSDs), users will notice degrading performance
> without an obvious cause, and it will be difficult to diagnose.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linuxmint/+bug/1332720/+subscriptions
>