KDE has a problem with correct calculation of used/available disk space.
My /home partition has 60GB but Dolphin calculates that I am using 69.5GB(!).

I store my backup in /home/backup. It is created with rsnapshot. The real weight of this folder is 4.6GB but Dolphin returns 17.4 – it counts in hard links which it should not.

Now I’m downloading some torrent of 22GB. Dolphin says the whole space is allocated (22GB) but that’s du -h that shows the real number – 4.1GB.

Conversely, Dolphin’s status bar shows nearly real space.

To recap: the real available space shows:
[*]KDE Partition Manager
[*]Dolphin status bar
[*]Filelight - a utility app
[*]df -h

But not only Dolphin has the problem. Probably KTorrent uses the same algorithm and I am told that I am run out of space.

Thanks for further tips.

Hm, interesting indeed.

Could you post more info such as your fstab, output of df -h and fdisk -l for starters and anything that you think may be of relevance?

fstab:

Code: Select all

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
/dev/sda5       /               ext4    errors=remount-ro 0       1
# /home was on /dev/sda7 during installation
UUID=c66c0ac9-49e3-434d-9987-8f79733cd490 /home           ext4    defaults        0       2
/dev/sda6       none            swap    sw              0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0

df -h:

Code: Select all

Filesystem            Size  Used Avail Use% Mounted on
/dev/sda5              14G  4.2G  9.0G  32% /
none                  934M  648K  933M   1% /dev
none                  943M  2.7M  940M   1% /dev/shm
none                  943M   92K  943M   1% /var/run
none                  943M     0  943M   0% /var/lock
/dev/sda7              60G   40G   17G  70% /home

fdisk -l:

Code: Select all

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe771e771

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        9730    78149633    5  Extended
/dev/sda5               1        1824    14647296   83  Linux
/dev/sda6            1824        1885      487424   82  Linux swap / Solaris
/dev/sda7            1885        9730    63012864   83  Linux

Could you also post the output of blkid (or perhaps sudo blkid) just to make sure.

EDITED - I had a senior moment...

Code: Select all

/dev/sda5: UUID="61b13787-31a3-4671-b904-f2af309877f4" TYPE="ext4"
/dev/sda6: UUID="7d9350af-09c3-42c0-87d5-66fbf1f79092" TYPE="swap"
/dev/sda7: UUID="c66c0ac9-49e3-434d-9987-8f79733cd490" TYPE="ext4"

Okay, all the pointers appear to be fine and what you said in your OP is, of course, correct.

I haven't had this happen to me so the following possibilities are mere conjecture:
1. a tmp or cache issue - would be fixed with a reboot
2. a dolphin issue - could be fixed by a) replacing your dolphinrc or b) reinstalling
3. install xdiskusage - a great du for X

I store my backup in /home/backup. It is created with rsnapshot. The real weight of this folder is 4.6GB but Dolphin returns 17.4 – it counts in hard links which it should not.

Looks like you identified that one - have you googled that issue?

Now I’m downloading some torrent of 22GB. Dolphin says the whole space is allocated (22GB) but that’s du -h that shows the real number – 4.1GB.

So Dolphin or rather your torrent client reserved the entire space.

Perhaps other people will suggest better solutions or even know what is going on. Whatever, keep us up-to-date.