From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard drive and maximum data percentage.
Date: Sat, 1 Feb 2025 15:15:58 -0600 [thread overview]
Message-ID: <948eaf97-a147-06f2-a482-528a71410fc9@gmail.com> (raw)
In-Reply-To: <fae9982e-ee0b-dd0e-94dc-a5e0726a1804@gmail.com>
Dale wrote:
> Howdy,
>
> As most know, I store a lot of data here. This is the two main file
> systems.
>
> %USED USED AVAILABLE TOTAL MOUNTED ON
> 87.5% 36.3T 5.2T 41.5T /home/dale/Desktop/Data
> 75.9% 35.8T 11.3T 47.1T /home/dale/Desktop/Crypt
>
> The top one has a drive on the way, well, will ship Monday and be here
> Wednesday or Thursday. Should complete tests and be online by Friday or
> so. I try not to go over 90%. I start saving money when it hits 80% or
> so. I've read that 80% is needing expansion. I notice that df and dfc
> show anything above 70% as red. I have went above 90% on occasion,
> usually when moving data around to balance out the volume. Thing is,
> most info I find is more about much smaller file systems. As you can
> see above, there is several TBs of space for the file system to do any
> housekeeping such as defragmenting and such. 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?
>
> By the way, data up there is about to be 4 hard drives. Crypt is still
> 3 but . . . you know how it is. I might add, my backup drive set is 4
> drives, each smaller. It will likely be 5 before long. I split up some
> files in data. Some goes onto a single drive. I have six drives for
> backups in total. I'm trying to replace smaller drives with either 14TB
> or 16TB drives. Fewer drives plus I can use smaller drives for backups
> and such. Rarely buy a drive now less than 12TB.
>
> Thoughts on when it is time to start expanding and keep data safe. One
> of these days, I may have to ask about the limits on file system size.
> O_O
>
> Thanks.
>
> Dale
>
> :-) :-)
>
Hard to believe no one has more up to date info on what is safe given
drives are so large now and file system improvements. I'd think having
a TB or two would be plenty, regardless of percentage, but not real
sure. Don't want to risk data testing the theory either.
Update: The new drive came in. It passed all the tests and is online.
dfc looks like this now for Data.
%USED USED AVAILABLE TOTAL MOUNTED ON
66.4% 37.1T 18.8T 55.9T /home/dale/Desktop/Data
May have to start adding two drives at a time. o_O 18Tb and larger
drives are to pricey still.
Dale
:-) :-)
next prev parent reply other threads:[~2025-02-01 21:17 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 [this message]
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
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=948eaf97-a147-06f2-a482-528a71410fc9@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