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 16:55:29 -0500 [thread overview]
Message-ID: <CAGfcS_k1517Yv22C0v-8wbnzDxHrPvN6w2kdaJTNtS9n+0s-Aw@mail.gmail.com> (raw)
In-Reply-To: <fae9982e-ee0b-dd0e-94dc-a5e0726a1804@gmail.com>
On Sun, Jan 26, 2025 at 1:15 PM Dale <rdalek1967@gmail.com> wrote:
> Still, given the large
> file systems in use, where should I draw the line and remain safe data
> wise? Can I go to 90% if needed? 95%? Is that to much despite the
> large amount of space remaining? Does the percentage really matter? Is
> it more about having enough space for the file system to handle its
> internal needs? Is for example 1 or 2TBs of free space enough for the
> file system to work just fine?
It really depends on the filesystem. For ext4 you can go all the way
to zero bytes free with no issues, other than application issues from
being unable to create files. (If you're talking about the root
filesystem, then the "application" includes the OS so that isn't
ideal.)
Some filesystems don't handle running out of space well. These are
usually filesystems that handle redundancy internally, but you really
need to look into the specifics. Are you running something other than
ext4 here?
The space free almost always takes into account filesystem overhead.
The issue is generally whether the filesystem can actually free up
space once it runs out completely (COW might want to allocate space
just to delete things, due to the need to not overwrite metadata in
place).
--
Rich
next prev parent reply other threads:[~2025-02-01 21:56 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 [this message]
2025-02-02 0:15 ` Dale
2025-02-02 0:29 ` Rich Freeman
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_k1517Yv22C0v-8wbnzDxHrPvN6w2kdaJTNtS9n+0s-Aw@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