From: nospam@needed.invalid   
      
   On Sun, 10/5/2025 9:55 AM, RobH wrote:   
   > On a separate desk top pc which runs 2 extra programs, 1 a weather station   
   and the other a cctv program.   
   >   
   > Out of curiosity, I wanted to see how much free space I had left on a 250Gb   
   ssd, so according to properties in the files app, I have 45Gb free space. So   
   then I ran disc analiser and it give me these figures:   
   >   
   > Kernel 479mb   
   > Modules 23Gb   
   > lib    28.5Gb   
   > usr    39.6   
   > CCTV    8.2kb   
   > weather program 4.1kb   
   >   
   > So the total usage there is approx 90Gb   
   >   
   > And in the centre of disc analyser it says 60.2|Gb   
   >   
   > My questions are why so little space left on my 250Gb ssd   
   > And why the differences between what properties say is 45Gb free space and   
   what is that 60.2Gb figure mean   
      
   But you don't want a disk analyser. These programs can crawl slash for you.   
   The "sudo" is so anything which only root can read, get analysed too.   
      
   sudo kdirstat /      #  Assuming we have a one disk system, and want to see   
   the file distribution   
   sudo qdirstat /      #  Same thing, from a different ecosystem.   
      
      "QDirStat is based on that code, but made independent of any KDE libraries   
   or infrastructure,   
       so it has much fewer library and package dependencies; basically only the   
   Qt 5 libs and libz,   
       both of which most Linux / BSD machines have installed anyway if there is   
   any graphical desktop installed."   
      
   The programs recursively descend a tree and total things up.   
      
   You can have a swapfile as in /swapfile or you can have a swap partition.   
   When you run the "top" command, you can see if a swapon -a was done   
   at boot and the swap partition(s) are loaded.   
      
   *******   
      
   The utility "gnome-disks" shows you the layout of your disk drive,   
   so you don't miss anything. While you can study mounted things   
   (mounted with respect to /), if something wasn't mounted it could   
   take up space and miss your forensic advances.   
      
   The "df" or diskfree command, tells you of component mounts in the system,   
   and for the partitions that are optional, can tell you whether they are   
   mounted at the moment.   
      
   Most sessions, usually see me using gnome-disks, to see which   
   partitions are mounted. A mounted partition seen in gnome-disks,   
   has a "fill line" indicating how filled it is, and you can read the   
   legend in the lower pane for details. The button on the left, in the   
   controls under the partition box row, the triangle can mount or umount   
   a partition you have clicked.   
      
   Be careful with gnome-disks. It contains a couple of power user   
   features which can be destructive. There is a bandwidth test,   
   which threatens to do R/W testing instead of R only speed   
   tests of a drive. And there is a button for "deleting partitions",   
   which is a pretty dangerous button to have in an interface. Whether   
   it has "interlocks" or "are you sure?" things or not, a partition   
   delete is a danger. You will need to learn how the tool works,   
   thoroughly, to really enjoy it and not cause a catastrophe.   
      
   Summary: You have a space gobbling partition which is not mounted.   
            Use gnome-disks, and spot the partition where you "can't see   
            the fill", which means it is not mounted at the moment.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)