From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard drive and maximum data percentage.
Date: Sat, 1 Feb 2025 19:29:43 -0500 [thread overview]
Message-ID: <CAGfcS_=whYhFFa4q7eVgf0W-iv-Ly7DmPZyuf8dj2Dvtgqnc-Q@mail.gmail.com> (raw)
In-Reply-To: <8762b502-c195-7bab-8d56-9876e11af9cd@gmail.com>
On Sat, Feb 1, 2025 at 7:15 PM Dale <rdalek1967@gmail.com> wrote:
>
> My thinking, even if I went to 95%, it should be OK given my usage. It
> might even be OK at 99%. Thing is, I know at some point, something is
> going to happen. I just been wondering what that point is and what it
> will do. Oh, I do use ext4.
If you're using ext4 and this is a dedicated filesystem that no
critical applications need to be able to write to, then there really
are no bad consequences for filling the entire disk. With ext4 if you
want to get the same back you just need to rm some file. Really the
only downside for you in this use case is not being able to cram
something onto it when you want to.
Now, if you were running btrfs or cephfs or some other exotic
filesystems, then it would be a whole different matter, as those
struggle to recover space when they get too full. Something like ceph
also trades free space for failover space if you lose a disk, so if
you want the cluster to self-heal you need free space for it to work
with (and you want it to still be 85% free or so even after losing a
disk),
--
Rich
next prev parent reply other threads:[~2025-02-02 0:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 18:15 [gentoo-user] Hard drive and maximum data percentage Dale
2025-02-01 21:15 ` Dale
2025-02-01 22:10 ` Mark Knecht
2025-02-01 23:51 ` Dale
2025-02-01 21:55 ` Rich Freeman
2025-02-02 0:15 ` Dale
2025-02-02 0:29 ` Rich Freeman [this message]
2025-02-02 1:40 ` Dale
2025-02-02 2:07 ` Rich Freeman
2025-02-02 11:00 ` Michael
2025-02-02 18:08 ` Dale
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='CAGfcS_=whYhFFa4q7eVgf0W-iv-Ly7DmPZyuf8dj2Dvtgqnc-Q@mail.gmail.com' \
--to=rich0@gentoo.org \
--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