Fish Posted December 23, 2008 Share Posted December 23, 2008 Just a query really, I don't think anything is wrong, but why is Gparted showing different values for disk usage compared to Conky (and incidentally, Thunar)? Link to comment Share on other sites More sharing options...
Lechio Posted December 23, 2008 Share Posted December 23, 2008 Run "df" and see who lies. Maybe the conky script is not well scripted and displays the info wrong, that would be my first guess. Would trust the accuracy of Gparted to be better than the one of a conky script. Link to comment Share on other sites More sharing options...
Fish Posted December 23, 2008 Author Share Posted December 23, 2008 fish@el-crappo-lappo:~$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 9690348 3271584 5930388 36% / none 383336 0 383336 0% /dev/shm /dev/sda5 13164720 4611324 7889916 37% /home /dev/sda2 5237188 3649828 1587360 70% /mnt/windows 192.168.1.66:/mnt/NAS_Media 77759232 70055776 1482720 98% /mnt/films 192.168.1.66:/mnt/NAS_MUSIC 37851232 29187648 5635488 84% /mnt/music fish@el-crappo-lappo:~$ :blink: Different again? Btw, Thunar agrees with Conky. Link to comment Share on other sites More sharing options...
ichi Posted December 23, 2008 Share Posted December 23, 2008 That probably has to do with ext3's reserved blocks, which are only available for priviledged processes. Check the -m parameter in man tune2fs. Link to comment Share on other sites More sharing options...
Fish Posted December 24, 2008 Author Share Posted December 24, 2008 I don't fully understand the concept, but it does seem to make some sense. So in effect, Gparted is showing the correct amount of free space, but df, Conky etc will only show the useable amount? Link to comment Share on other sites More sharing options...
ichi Posted December 24, 2008 Share Posted December 24, 2008 Maybe gparted is running as root? Anyway, from the user processes point of view reserved blocks don't count as free space so it makes sense to not show them as such. If you take values from the df output, summing used and available space for / doesn't give the total partition size (while it does on /mnt/windows). You are missing exactly a 5% of the total size, which happens to be the default size for ext3's reserved blocks. Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted December 24, 2008 Veteran Share Posted December 24, 2008 (edited) Well, df will give different results if you use one measuring system over another (1000 vs. 1024 bytes/K). What are the outputs of df -h versus df -H ? Looking at your values again, I am nearly certain that this is the disparity. 8,100,000,000 bytes expressed using 1024 bytes/K is about 7.54GB. Expressed using 1000 bytes/K yields 8.10GiB. Seem plausible? EDIT: Incidentally, and I am not sure why, but my gparted shows "GiB" and "MiB" units for data sizes, whereas yours just shows "GB" and "MB". :unsure: Edited December 24, 2008 by markjensen Link to comment Share on other sites More sharing options...
Fish Posted December 24, 2008 Author Share Posted December 24, 2008 Gparted is indeed running as root. It crossed my mind that the difference might also be to do with how a k/b is measured. Well, I've learned something new today! Mark, not sure why my Gparted is different to yours. Mine is at version 0.4.1, perhaps it's an older version that's in the Arch repo? Link to comment Share on other sites More sharing options...
Recommended Posts