From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What are common SSDs does and don'ts.
Date: Sun, 23 Mar 2025 16:41:58 -0500 [thread overview]
Message-ID: <0366e58b-826c-3ec4-bc94-20a992d21dd0@gmail.com> (raw)
In-Reply-To: <5873402.DvuYhMxLoT@rogueboard>
Michael wrote:
> On Sunday, 23 March 2025 01:48:01 Greenwich Mean Time Dale wrote:
>> Michael wrote:
>>> Finally, consider TRIM being run on a cron job, or better use something
>>> like the SSDcronTRIM script once a month to decide and execute fstrim if
>>> needed.
> [snip ...]
>
>> The only thing on SSD is the OS itself. I have partitions for /efi,
>> /boot with ext2, / and /var with ext4. I'll set up fstrim later on.
>> Given I have a 1TB stick and left well over 100GBs unused, I should have
>> room left over to last a while. On my todo list tho. Would once a
>> month be often enough tho? I update each weekend. Other than that, not
>> much changes really. /home and such is on spinning rust still. If I
>> did daily updates, might be a better plan. Once a week, maybe monthly
>> will be OK.
> Even once every 3-6 months would be more than enough. The SSDcronTRIM will
> check if your disk is filling up and will only run fstrim when/if it is
> needed.
>
> https://chmatse.github.io/SSDcronTRIM/
That's not in the Gentoo tree. Hmmmmm.
I ran fstrim on my root and var partitions and got this.
root@Gentoo-1 / # fstrim -v /
/: 13.7 GiB (14676369408 bytes) trimmed
root@Gentoo-1 / # fstrim -v /var
/var: 43.9 GiB (47162359808 bytes) trimmed
root@Gentoo-1 / #
It looks like /var changes more than root does. I kinda wish I just
could run it on the whole m.2 stick and it do its thing regardless of
mount point. From the looks of the man page tho, that isn't a option.
I still haven't figured out how I want to setup the newest m.2 stick.
I'm thinking about using dm-setup to encrypt it, or most of it anyway.
Dale
:-) :-)
next prev parent reply other threads:[~2025-03-23 21:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 18:50 [gentoo-user] What are common SSDs does and don'ts Dale
2025-03-22 19:29 ` Mark Knecht
2025-03-22 21:37 ` Michael
2025-03-23 1:48 ` Dale
2025-03-23 9:00 ` Michael
2025-03-23 21:41 ` Dale [this message]
2025-03-23 22:15 ` Nate Eldredge
2025-03-23 22:32 ` Frank Steinmetzger
2025-03-23 23:24 ` Dale
2025-03-31 21:27 ` Frank Steinmetzger
2025-04-01 0:44 ` Dale
2025-04-01 10:01 ` Peter Humphrey
2025-04-01 10:12 ` Dale
2025-04-01 10:24 ` Peter Humphrey
2025-04-01 12:56 ` Dale
2025-04-01 13:13 ` Peter Humphrey
2025-04-02 3:33 ` Dale
2025-04-02 11:13 ` Peter Humphrey
2025-04-01 11:04 ` Michael
2025-04-01 13:03 ` Dale
2025-04-01 15:44 ` Michael
2025-04-02 4:04 ` Dale
2025-04-02 8:29 ` Michael
2025-04-07 18:28 ` Dale
2025-04-01 22:46 ` Frank Steinmetzger
2025-04-01 23:08 ` Frank Steinmetzger
2025-04-02 4:03 ` Dale
2025-03-23 4:34 ` Matt Jolly
2025-03-23 6:56 ` netfab
2025-03-23 7:01 ` Dale
2025-03-23 7:03 ` netfab
2025-03-23 22:46 ` Frank Steinmetzger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0366e58b-826c-3ec4-bc94-20a992d21dd0@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox