this post was submitted on 18 Oct 2023
201 points (97.2% liked)

linuxmemes

21273 readers
1251 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
    [โ€“] treadful@lemmy.zip 2 points 1 year ago (1 children)

    Yeah, the man page doesn't really help me out.

       fstrim is used on a mounted filesystem to discard (or "trim")
       blocks which are not in use by the filesystem. This is useful for
       solid-state drives (SSDs) and thinly-provisioned storage.
    
       By default, fstrim will discard all unused blocks in the
       filesystem. Options may be used to modify this behavior based on
       range or size, as explained below.
    
       The mountpoint argument is the pathname of the directory where
       the filesystem is mounted and is required when -A, -a, --fstab,
       or --all are unspecified.
    
       Running fstrim frequently, or even using mount -o discard, might
       negatively affect the lifetime of poor-quality SSD devices. For
       most desktop and server systems a sufficient trimming frequency
       is once a week. Note that not all devices support a queued trim,
       so each trim command incurs a performance penalty on whatever
       else might be trying to use the disk at the time.
    

    For instance, why would unused blocks not be discarded? And what does "discarded" even mean in this context? But it does recommend against using it for SSDs so I think I'll skip it.

    [โ€“] naeap@sopuli.xyz 1 points 1 year ago

    "this is useful for solid-state drives"
    Where is it not recommended?

    Or did I just miss something?