Announcement

Collapse
No announcement yet.

Ubuntu 14.04 Finally Enables SSD TRIM By Default

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Ubuntu 14.04 Finally Enables SSD TRIM By Default

    Phoronix: Ubuntu 14.04 Finally Enables SSD TRIM By Default

    The 14.04 "Trusty Tahr" operating system release will be the first version of Ubuntu Linux shipping SSD TRIM support by default...

    http://www.phoronix.com/vr.php?view=MTU0NjA

  • #2
    too early ?

    adding discard options to ext4 on SSD is not a good idea.
    when removing a lot of small files (make clean ?), it can freeze a computer for 5-10min.
    it's the case on my laptop (quad-core with 6G RAM), and a better method is to add fstrim to a crontab.

    when I say freeze, I mean all keystroke/click are delayed by 30-40s, so it's completely unusable.

    Comment


    • #3
      Originally posted by jockinator View Post
      adding discard options to ext4 on SSD is not a good idea.
      when removing a lot of small files (make clean ?), it can freeze a computer for 5-10min.
      it's the case on my laptop (quad-core with 6G RAM), and a better method is to add fstrim to a crontab.

      when I say freeze, I mean all keystroke/click are delayed by 30-40s, so it's completely unusable.
      I don't have this problem on my desktop (256 GiB Samsung 840 Pro, i7-2600 K, 8GB of RAM, running Xubuntu 13.10). I don't notice anything like excessive RAM usage or something like that.

      Comment


      • #4
        So why could Windows add this in 2009?

        Comment


        • #5
          No problem here either

          Originally posted by jockinator View Post
          adding discard options to ext4 on SSD is not a good idea.
          when removing a lot of small files (make clean ?), it can freeze a computer for 5-10min.
          it's the case on my laptop (quad-core with 6G RAM), and a better method is to add fstrim to a crontab.

          when I say freeze, I mean all keystroke/click are delayed by 30-40s, so it's completely unusable.
          I am with Calinou, I have never had that issue. And even after months of updates apt-get clean is instantaneous. I do not compile a lot, and my projects are relatively small, but make clean is also instantaneous for me.

          I am using Debian Sid/Jessie not Ubuntu.

          For 99% of users discard is a good idea. For people like you, you are smart enough to edit fsatb and use crontab instead.

          Comment


          • #6
            I use Gentoo and I never had such an issue on my Intel X25-M G2
            ## VGA ##
            AMD: X1950XTX, HD3870, HD5870
            Intel: GMA45, HD3000 (Core i5 2500K)

            Comment


            • #7
              So they're using fstrim and a daily or weekly cron job.

              Does anyone know how Windows does it? I keep hearing that neither discard nor fstrim with a cron job are ideal (which was why there was such a long debate on whether or not to enable TRIM by default) and Windows does it completely differently but no one knows how.

              Comment


              • #8
                Originally posted by Ferdinand View Post
                So why could Windows add this in 2009?
                Linux could do that too. It only didn't because you didn't write required patches back in 2009. Linux is free mate, nobody is stopping you from adding support for anything.

                Comment


                • #9
                  Originally posted by prodigy_ View Post
                  Linux could do that too. It only didn't because you didn't write required patches back in 2009. Linux is free mate, nobody is stopping you from adding support for anything.
                  Its actually funny cause according to: http://en.wikipedia.org/wiki/Trim_%2...system_support Linux had TRIM support before Windows did :P

                  Comment


                  • #10
                    Originally posted by prodigy_ View Post
                    Linux could do that too. It only didn't because you didn't write required patches back in 2009. Linux is free mate, nobody is stopping you from adding support for anything.
                    Linux is free and is all about choice. Your comment assumes that my choice of paying for an expert to do it for me does not exist in the Linux world. I hope you will never use that 'argument' again.

                    Comment


                    • #11
                      Originally posted by jockinator View Post
                      adding discard options to ext4 on SSD is not a good idea.
                      when removing a lot of small files (make clean ?), it can freeze a computer for 5-10min.
                      it's the case on my laptop (quad-core with 6G RAM), and a better method is to add fstrim to a crontab.
                      If you had read the Google+ post, you would know that they actually do this. The are aware of the fact that kernel managed trim has issues.

                      Comment


                      • #12
                        Originally posted by brent View Post
                        If you had read the Google+ post, you would know that they actually do this. The are aware of the fact that kernel managed trim has issues.
                        oh you're right, the source https://blueprints.launchpad.net/ubu...1-ssd-trimming said it is a cron job using fstrim, but the phoronix article is inaccurate :

                        Supporting TRIM requires setting the discard mount option for using TRIM when deleting files as it's not enabled by default

                        I observe freeze on my work PC, when I build a whole Android tree, and then delete the "out/" folder (~30GB, ), but that's a known issue. Most blog posts I've seen on TRIM on Linux, choose fstrim over discard mount option.

                        Comment


                        • #13
                          Originally posted by jockinator View Post
                          adding discard options to ext4 on SSD is not a good idea.
                          when removing a lot of small files (make clean ?), it can freeze a computer for 5-10min.
                          it's the case on my laptop (quad-core with 6G RAM), and a better method is to add fstrim to a crontab.
                          If I understand things correctly, this problem was addressed in Serial ATA revision 3.1 (released in July 2011) with the introduction of the Queued Trim Command. Support for the Queued Trim Command was introduced in the 3.12 kernel - see https://lkml.org/lkml/2013/9/3/277

                          Comment

                          Working...
                          X