Bug 250875 - Dolphin calculating file size of hardlinks resulting in Tib of data on a 400 GiB HDD
Summary: Dolphin calculating file size of hardlinks resulting in Tib of data on a 400 ...
Status: RESOLVED DUPLICATE of bug 67939
Alias: None
Product: kfile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR minor
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 266630 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-09-11 14:46 UTC by safttuete
Modified: 2011-10-07 10:34 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description safttuete 2010-09-11 14:46:32 UTC 
Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

As the summary explains Dolphins expands my hdd for free :D

The links are created by BackInTime-0.9.26-r2.

Excluding the backintime folder shows a realistic file size.

Reproducible: Always

Steps to Reproduce:
1. Select a folder with hardlinks in Dolphin
2. Check the file size with the attributes menu (alt+enter)
3. see Dolphin resizing your HDD beyond any limits :D

Actual Results:  
Filesize is calculated wrong

Expected Results:  
"ignore" hardlinks or better, recognize those as ones and only count them once.

compiled from gentoo sources.
Didn't report it on bugs.gentoo.org as it seems to be an upstream issue.
Comment 1 Peter Penz 2010-09-23 11:58:26 UTC 
(internal note: must be fixed in KPropertiesDialog)
Comment 2 Frank Reininghaus 2011-02-19 11:41:09 UTC 
*** Bug 266630 has been marked as a duplicate of this bug. ***
Comment 3 Wojciech Ryrych 2011-07-24 15:15:30 UTC 
KDE 4.6.5 – I have the same problem. The real size of my backup folder is 4.6GB but Dolphin shows that it’s 17GB.

Interestingly, the bar in the status bar showing available space shows nearly real space.
Comment 4 Christoph Feck 2011-10-07 10:34:33 UTC 

*** This bug has been marked as a duplicate of bug 67939 ***