Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: fstrim.timer

  1. #11
    Join Date
    Sep 2012
    Posts
    4,734

    Default Re: fstrim.timer

    Quote Originally Posted by malcolmlewis View Post
    Btrfs detects and adjusts the mount options for a ssd;
    Code:
    (rw,relatime,ssd,space_cache,subvolid=nnn,subvol=/@/mountpoint)
    "ssd" is unrelated to TRIM/discard. It changes internal space allocation algorithm in a way that was believed to be more SSD friendly. Recently there were reports that this algorithm may lead to heavy fragmentation and early out-of-space condition and it is questionable whether it is needed with modern SSD at all. Also heuristic to detect SSD is far from being perfect. It is based on "rotational" flag for device; and kernel will always return "non-rotational" unless it can verify that it is local rotational HDD. So any virtual/SAN/... device will be considered "SSD" in this case.

  2. #12

    Default Re: fstrim.timer

    Wow, I thought the "trim wars" were over for some years now! Fun to see that there are still high-end discussions on the "topic"....
    Kind regards

    raspu

  3. #13
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    25,202
    Blog Entries
    15

    Default Re: fstrim.timer

    Quote Originally Posted by suse_rasputin View Post
    Wow, I thought the "trim wars" were over for some years now! Fun to see that there are still high-end discussions on the "topic"....
    Hi
    It still lurks there are still devices that are blacklisted as well... I did use it a while back with ext4 on a SSD, not bothered to change any of the defaults and systems run fine...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  4. #14

    Default Re: fstrim.timer

    Same here, some Samsung EVO 8xx, some Intels since 2015/16, never thought about it much, have a look at SMART from time to time, no problems with performance yet, most systems running 24/7, but no servers. Installed a 42.x to a USB stick (64 GB USB3 Sandisk, the small one with metal case) and used for surfing 1 year, then system turned to read-only in December :-D Now I use an SSD...
    Kind regards

    raspu

  5. #15
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    25,202
    Blog Entries
    15

    Default Re: fstrim.timer

    On Sat 05 Jan 2019 05:56:03 AM CST, arvidjaar wrote:


    malcolmlewis;2890817 Wrote:
    > Btrfs detects and adjusts the mount options for a ssd;
    > >

    Code:
    --------------------
    > >

    > (rw,relatime,ssd,space_cache,subvolid=nnn,subvol=/@/mountpoint)
    >

    --------------------
    > >

    "ssd" is unrelated to TRIM/discard. It changes internal space allocation
    algorithm in a way that was believed to be more SSD friendly. Recently
    there were reports that this algorithm may lead to heavy fragmentation
    and early out-of-space condition and it is questionable whether it is
    needed with modern SSD at all. Also heuristic to detect SSD is far from
    being perfect. It is based on "rotational" flag for device; and kernel
    will always return "non-rotational" unless it can verify that it is
    local rotational HDD. So any virtual/SAN/... device will be considered
    "SSD" in this case.


    Hi
    Yes, that was just the defaults as installed, I did read something
    about space allocation awhile back.. my SSD's are all older ones now,
    but still going fine

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  6. #16
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    1,996

    Talking Re: fstrim.timer

    Personally, I only have the systemd “fstrim.timer” service enabled on a Desktop system with an ext4 system partition on a SSD.
    • “OnCalendar=monthly” -- IOW fstrim is only run once a month (*-*-01 00:00:00) -- usually on booting …


    If I had a Btrfs system partition on a SSD then, I would tend to use the systemd “btrfs-trim.timer” service and disable the “fstrim.timer” service …

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •