this post was submitted on 18 Oct 2023
214 points (97.3% liked)

linuxmemes

21172 readers
1041 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] possiblylinux127@lemmy.zip 16 points 1 year ago (1 children)

    Doesn't btrfs do this already?

    [–] SuperIce@lemmy.world 11 points 1 year ago (1 children)

    Yeah, it's unnecessary with btrfs on somewhat recent kernels since it now enables discard=async by default.

    [–] bazsy@lemmy.world 4 points 1 year ago

    It is not necessary but still better to run both online discard and batched fstrim. from man:

    Also, a device may ignore the TRIM command if the range is too small, so running a batch discard has a greater probability of actually discarding the blocks.