public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Finally got a SSD drive to put my OS on
Date: Thu, 20 Apr 2023 04:48:07 -0500	[thread overview]
Message-ID: <901bd323-6211-c3be-adf2-1fa9b26f77ef@gmail.com> (raw)
In-Reply-To: <7458305e-bc06-0206-3a20-196339a7f24c@cox.net>

eric wrote:
> On 4/19/23 21:23, Dale wrote:
>> Mark Knecht wrote:
>>>
>>> > I wonder.  Is there a way to find out the smallest size file in a
>>> directory or sub directory, largest files, then maybe a average file
>>> size???  I thought about du but given the number of files I have
>>> here, it would be a really HUGE list of files. Could take hours or
>>> more too.  This is what KDE properties shows.
>>>
>>> I'm sure there are more accurate ways but
>>>
>>> sudo ls -R / | wc
>>>
>>> give you the number of lines returned from the ls command. It's not
>>> perfect as there are blank lines in the ls but it's a start.
>>>
>>> My desktop machine has about 2.2M files.
>>>
>>> Again, there are going to be folks who can tell you how to remove
>>> blank lines and other cruft but it's a start.
>>>
>>> Only takes a minute to run on my Ryzen 9 5950X. YMMV.
>>>
>>
>> I did a right click on the directory in Dolphin and selected
>> properties.  It told me there is a little over 55,000 files.  Some
>> 1,100 directories, not sure if directories use inodes or not.
>> Basically, there is a little over 56,000 somethings on that file
>> system.  I was curious what the smallest file is and the largest. No
>> idea how to find that really.  Even du separates by directory not
>> individual files regardless of directory.  At least the way I use it
>> anyway.
>>
>> If I ever have to move things around again, I'll likely start a
>> thread just for figuring out the setting for inodes.  I'll likely
>> know more about the number of files too.
>>
>> Dale
>>
>> :-)  :-)
>
> If you do not mind using graphical solutions, Filelight can help you
> easily visualize where your largest directories and files are residing.
>
> https://packages.gentoo.org/packages/kde-apps/filelight
>
>> Visualise disk usage with interactive map of concentric, segmented rings 
>
> Eric
>
> .
>

There used to be a KDE app that worked a bit like this.  I liked it but
I think it died.  I haven't seen it in ages, not long after the switch
from KDE3 to KDE4 I think.  Given the volume of files and the size of
the data, I wish I could zoom in sometimes.  Those little ones disappear. 

Thanks for that info. Nifty. 

Dale

:-)  :-) 


  reply	other threads:[~2023-04-20  9:48 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-15 22:47 [gentoo-user] Finally got a SSD drive to put my OS on Dale
2023-04-15 23:24 ` Mark Knecht
2023-04-15 23:44   ` thelma
2023-04-16  1:47 ` William Kenworthy
2023-04-16  7:18   ` Peter Humphrey
2023-04-16  8:43     ` William Kenworthy
2023-04-16 15:08       ` Mark Knecht
2023-04-16 15:29         ` Dale
2023-04-16 16:10           ` Mark Knecht
2023-04-16 16:54             ` Dale
2023-04-16 18:14               ` Mark Knecht
2023-04-16 18:53                 ` Dale
2023-04-16 19:30                   ` Mark Knecht
2023-04-16 22:26                     ` Dale
2023-04-16 23:16                       ` Frank Steinmetzger
2023-04-17  1:14                         ` Dale
2023-04-17  9:40                           ` Wols Lists
2023-04-17 17:45                             ` Mark Knecht
2023-04-18  0:35                               ` Dale
2023-04-18  8:03                               ` Frank Steinmetzger
2023-10-07  7:22                         ` Dale
2023-04-16 17:46         ` Jorge Almeida
2023-04-16 18:07         ` Frank Steinmetzger
2023-04-16 20:22           ` Mark Knecht
2023-04-16 22:17             ` Frank Steinmetzger
2023-04-17  0:34               ` Mark Knecht
2023-04-18 14:52 ` [gentoo-user] " Nikos Chantziaras
2023-04-18 15:05   ` Dale
2023-04-18 15:36     ` Nikos Chantziaras
2023-04-18 20:01       ` Dale
2023-04-18 20:53         ` Wol
2023-04-18 22:13           ` Frank Steinmetzger
2023-04-18 23:08             ` Wols Lists
2023-04-19  1:15               ` Dale
2023-04-18 20:57         ` Mark Knecht
2023-04-18 21:15           ` Dale
2023-04-18 21:25             ` Mark Knecht
2023-04-19  1:36               ` Dale
2023-04-18 22:18     ` Frank Steinmetzger
2023-04-18 22:41       ` Frank Steinmetzger
2023-04-19  1:45       ` Dale
2023-04-19  8:00         ` Nikos Chantziaras
2023-04-19  9:42           ` Dale
2023-04-19 10:34           ` Peter Humphrey
2023-04-19 17:14             ` Mark Knecht
2023-04-19 17:59             ` Dale
2023-04-19 18:13               ` Mark Knecht
2023-04-19 19:26                 ` Dale
2023-04-19 19:38                   ` Nikos Chantziaras
2023-04-19 20:00                     ` Mark Knecht
2023-04-19 22:13                       ` Frank Steinmetzger
2023-04-19 23:32                         ` Dale
2023-04-20  1:09                           ` Mark Knecht
2023-04-20  4:23                             ` Dale
2023-04-20  4:41                               ` eric
2023-04-20  9:48                                 ` Dale [this message]
2023-04-20 23:02                               ` Wol
2023-04-20  8:55                             ` Frank Steinmetzger
2023-04-20  8:52                           ` Frank Steinmetzger
2023-04-20  9:29                             ` Dale
2023-04-20 10:08                               ` Peter Humphrey
2023-04-20 10:59                                 ` Dale
2023-04-20 13:23                                   ` Nikos Chantziaras
2023-04-20 12:23                               ` Frank Steinmetzger
2023-04-20  9:46               ` Peter Humphrey
2023-04-20  9:49                 ` Dale
2023-04-18 17:52   ` Mark Knecht

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=901bd323-6211-c3be-adf2-1fa9b26f77ef@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