Permanently Deleted
Permanently Deleted
Permanently Deleted
Permanently Deleted
Permanently Deleted
Trim support is standard. Any kernel released in the past 15 years or so will have trim support built in. So that's not something you should worry about.
How trimming is triggered is another matter, and is distro dependent. On Arch and Debian at least there is a weekly systemd timer that runs the fstrim
command on all trimmable filesystems. You can check it if's enabled with: systemctl list-unit-files fstrim.timer
. I can't tell how other distributions handle that. On Debian derived ones, I imagine it's similar, on something like Slackware, which is systemd-less and more hands-off in its approach, you may have to schedule fstrim
yourself, or run it manually occasionally.
There is also the discard
mount option that you can add in /etc/fstab
, which enables automatic synchronous trimming every time blocks are deleted, but its use is discouraged because it carries a performance penalty.
Hope that answers your question.
deleted by creator
the Arch wiki has some info. Not too sure but i think enabling the systemd timer is enough.
not sure about manual but on ArchLinux and NixOS, TRIM can be automatically handled with BTRFS options:discard=async:
not sure if this helps but I'll be open sourcing my NixOS build and configuration.nix files in a bit(after school schedule stablizes)
There are some differences between distros as to whether TRIM is enabled by default or not (I've read Ubuntu enables it by default, but Debian does not). That said, depending on what file-system your ssd is formatted with it may be enabled by default at that level. The most-often recommended file-systems for SSDs are Btrfs and F2FS, both of which support and enable TRIM by default (as of Linux 6.2 for Btrfs, so if you are running an older kernel version you might need to manually enable it). I think most distro installers support using Btrfs as the main file-system, but F2FS is a bit more hit and miss I think. Safest bet would be to investigate once you settle on a distro, but support should be pretty standard, even if it's not enabled by default.
Can't answer your question since it's not something I ever thought about but I recently, within the last 2 weeks, started the same thing. I tried Mint and EndeavorOS so far and honestly I probably won't leave EndeavorOS again. I installed it first. Confused the fuck out of myself because years ago I use Ubuntu so I had that like hard coded in me and couldn't get my head around arch. After playing with Mint for a week or so I'm back on EndeavorOS and I love it. I really really want to switch my main PC over but I have a Plex server and audio book shelf server running there as well as atleast 1 game that playing on Linux just isn't possible since Bungie will ban you for running destiny 2 on Linux.
deleted by creator
would consider myself very much a noob and I'm bumbling my way through it. Just kinda worked my way through it and pretty sure I broke my mint install a bit before hopping to EndeavorOS and will probably break this one before I'm done as well.
That is so bizarre to me. According to this article, Destiny 2 was already playable on Linux when it was officially ported to Google Stadia, and no one, not even Bungie, can explain why they won't support it on Linux or Steam Deck, much less ban a player for trying. That's crazy.
Yeah I have no idea either. From what I've seen online it's something to do with the anti cheat battleye but that runs on Linux so it's basically just them telling the Linux community to go pound sand.
Edited
lsblk --discard
to check support and non zero DISC returns mean TRIM supported.
And then you need to add Then enable discard
options to supported partitions in /etc/fstab.fstrim.timer
with systemctl
. And it will automatically run weekly. You can edit the run frequency by editing the fstrim.timer
file.
This is what I have done from reading Arch wiki. https://wiki.archlinux.org/title/Solid_state_drive#TRIM
You typically use either discard
or the fstrim.timer
, but not both at the same time.
Using the discard
option means that trims are being done on the fly every time blocks are deleted, using fstrim.timer
means that trims are being done periodically. The former carries a performance penalty, so it's usually not recommended unless you need it (for example, if you regularly do huge amounts of writes and deletes on this drive).
Thanks for this. I got confused writhing this as I used discard
on my previous install.