Created attachment 140252 [details] Initial view SUMMARY Display unusable disk space reserved for reserved blocks, inode blocks etc in "Initial view" of filelight app for applicable filesystems like ext4 etc. On my PC for /dev/sda2 ext4 partition of 867.39 GiB, the reserved block count is "11368998*4096 bytes= 46567415808 bytes= 43.3693 gibibytes", inode count is "56852480*256 bytes=14554234880 bytes= 13.5547 gibibytes" which is lot of disk space. If above unusable disk space is shown in filelight app, then users can know where the disk space is utilized & can atleast modify the reserved block count, also when reinstalling the OS. New users can find this feature helpful. Also for /dev/sda2 mounted at "/", In "Initial view" filelight displays used disk space as 842.3 GiB including reserved blocks etc, but in "Concentric rings view" actual used disk space is 794.5 GiB. Please see the attached screenshots. EXPECTED RESULT Display disk space utilized by Reserved blocks, Inode blocks, Journal blocks etc. or show it as filesystem reserved disk space in Initial view of filelight app. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-63-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz Memory: 3.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 ADDITIONAL INFORMATION
Created attachment 140253 [details] Concentric rings view
output of tune2fs -l /dev/sda2: tune2fs 1.45.5 (07-Jan-2020) Filesystem volume name: <none> Last mounted on: / Filesystem UUID: f8e66549-c5db-4c42-b729-15601980172f Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 56852480 Block count: 227379968 Reserved block count: 11368998 Free blocks: 14115771 Free inodes: 55628719 First block: 0 Block size: 4096 Fragment size: 4096 Group descriptor size: 64 Reserved GDT blocks: 1024 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Sun Oct 21 12:57:56 2018 Last mount time: Thu Jul 22 13:35:57 2021 Last write time: Thu Jul 22 19:05:49 2021 Mount count: 1503 Maximum mount count: -1 Last checked: Sun Oct 21 12:57:56 2018 Check interval: 0 (<none>) Lifetime writes: 3144 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 32 Desired extra isize: 32 Journal inode: 8 First orphan inode: 27264217 Default directory hash: half_md4 Directory Hash Seed: ab9a972f-9846-415b-8578-388e3a3a6ee5 Journal backup: inode blocks Checksum type: crc32c Checksum: 0xfae01655
Git commit 38a71d1cbd46964f47eac1377788ebaabc5956d8 by Harald Sitter. Committed on 19/04/2022 at 13:32. Pushed by sitter into branch 'master'. replace previous summary with tidy overview widget it occurred to us that the old disk view was fishy on a number of levels - it had a non exhaustive filter list of bad mounts - this then raised the question why the mounts are missing (when e.g. the user expected them to be there) - the free space on a partition is not reflective of the space filelight will be able to determine the use of (e.g. when +x is missing on a dir that dir will be missing from the fileview) - when talking about bind mounts (such as inside a sandbox) the two sizes will almost never add up - when inside a sandbox potentially only one valid path is available ($home) so having the previous view was slightly weird the grand new overview widget simply displays three buttons to get right into scanning root, home, or a custom path. root is hidden inside a sandbox. this preserves most of the spirit of what the previous view wanted to do while scaling better and doing away with judgment calls on the edge cases such as bind mounts Related: bug 452275, bug 440152, bug 426594 M +1 -0 CMakeLists.txt M +2 -2 src/CMakeLists.txt M +24 -28 src/mainWindow.cpp M +4 -4 src/mainWindow.h A +71 -0 src/overviewWidget.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] A +23 -0 src/overviewWidget.h [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] M +0 -2 src/radialMap/labels.cpp M +1 -28 src/radialMap/map.cpp M +1 -2 src/radialMap/map.h M +2 -3 src/radialMap/widget.cpp M +1 -6 src/radialMap/widget.h M +22 -43 src/radialMap/widgetEvents.cpp D +0 -183 src/summaryWidget.cpp D +0 -40 src/summaryWidget.h https://invent.kde.org/utilities/filelight/commit/38a71d1cbd46964f47eac1377788ebaabc5956d8