From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting maximum space out of a hard drive
Date: Thu, 18 Aug 2022 21:03:20 -0500 [thread overview]
Message-ID: <57a9895b-9357-17f1-8fb5-d0ede952eefc@gmail.com> (raw)
In-Reply-To: <CAGfcS_m0BNWQ10uptnH-T=QzWi6OWFA7WPeB_ZKutM0mzFLtJQ@mail.gmail.com>
Rich Freeman wrote:
> On Thu, Aug 18, 2022 at 2:04 PM Dale <rdalek1967@gmail.com> wrote:
>>
>> Part. # Size Partition Type Partition Name
>> ----------------------------------------------------------------
>> 1007.0 KiB free space
>> 1 9.1 TiB Linux filesystem 10Tb
>> 1007.5 KiB free space
>>
>>
>> I'm not sure why there seems to be two alignment spots. Is that
>> normal? Already, there is almost 1TB lost somewhere.
> 10 TB = 9.09495 TiB. You aren't missing much of anything.
>
> And no, I don't want to get into a religious war over base 2 vs base
> 10, and why it would be confusing if a tape that could store 10MB/m
> didn't store 10kB/mm but instead stored 10.24 kB/mm.
>
Well, I realize it would be less than advertised but I just want to
maximize it as much as I can. I found the -m option for the file system
a good while back and it saves a lot on these larger drives. Since this
is a external drive, no point in reserving any root space, since root
will likely never access it after the file system is put on it.
Nice to know it is a conversion thing going on tho. ;-)
Dale
:-) :-)
next prev parent reply other threads:[~2022-08-19 2:03 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 18:04 [gentoo-user] Getting maximum space out of a hard drive Dale
2022-08-18 18:18 ` Rich Freeman
2022-08-19 2:03 ` Dale [this message]
2022-08-19 4:26 ` David Haller
2022-08-24 22:45 ` Frank Steinmetzger
2022-08-25 6:22 ` William Kenworthy
2022-08-25 12:43 ` Dale
2022-08-25 12:52 ` Rich Freeman
2022-08-25 15:10 ` Jack
2022-08-25 18:59 ` Dale
2022-08-25 21:08 ` Rich Freeman
2022-08-25 23:59 ` Dale
2022-08-26 0:15 ` Mark Knecht
2022-08-26 11:26 ` Dale
2022-08-26 11:55 ` Gerrit Kuehn
2022-08-26 12:07 ` Rich Freeman
2022-08-26 23:07 ` Dale
2022-08-26 14:09 ` Mark Knecht
2022-08-26 14:25 ` Rich Freeman
2022-08-26 14:40 ` Mark Knecht
2022-08-26 23:20 ` Dale
2022-08-26 23:37 ` Mark Knecht
2022-08-27 1:16 ` Mark Knecht
2022-08-27 23:30 ` Dale
2022-08-28 9:27 ` Michael
2022-08-28 21:07 ` Frank Steinmetzger
2022-08-28 21:33 ` Wol
2022-08-28 21:53 ` Mark Knecht
2022-08-28 23:31 ` Wol
2022-08-28 21:34 ` Frank Steinmetzger
2022-08-29 5:49 ` Dale
2022-08-29 14:42 ` Frank Steinmetzger
2022-08-29 21:28 ` Dale
2022-08-30 14:26 ` Frank Steinmetzger
2022-08-25 22:41 ` Wols Lists
2022-08-25 23:56 ` Dale
2022-08-26 7:24 ` Wols Lists
2022-08-26 11:27 ` Dale
2022-08-26 13:35 ` Wols Lists
2022-08-26 4:47 ` David Haller
2022-08-18 18:20 ` Andreas Fink
2022-08-20 19:15 ` Dale
2022-08-20 20:57 ` Rich Freeman
2022-08-25 3:44 ` Dale
2022-08-20 21:46 ` Grant Taylor
2022-08-20 21:57 ` Grant Taylor
2022-08-20 22:45 ` Dale
2022-08-21 4:22 ` William Kenworthy
2022-08-21 5:34 ` Grant Taylor
2022-08-21 9:26 ` William Kenworthy
2022-08-21 10:09 ` Dale
2022-08-21 16:47 ` Dale
2022-08-21 5:27 ` Grant Taylor
2022-08-24 22:39 ` Frank Steinmetzger
2022-08-24 22:50 ` Wol
2022-08-22 14:50 ` Laurence Perkins
2022-08-22 15:02 ` Rich Freeman
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=57a9895b-9357-17f1-8fb5-d0ede952eefc@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