I would ask whether you realize you’re on a linux community, but you referred to a man page as a wiki article so you are clearly lost.
The first paragraph past the link is a summary of the function of the program.
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.
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.
and what does that achieve?
It’s a systemd timer included within Arch that runs fstrim every week.
wow such a great, short and understandable explanation that doesn’t link to a wiki article that no one will voluntarily read
I would ask whether you realize you’re on a linux community, but you referred to a
manpage as a wiki article so you are clearly lost.The first paragraph past the link is a summary of the function of the program.
Yeah, the man page doesn’t really help me out.
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.
“this is useful for solid-state drives”
Where is it not recommended?
Or did I just miss something?