du / dust disagreement

[ammaraziz]

Hi Bootandy,

Thanks for creating and maintaining dust it is excellent piece of software.

I am finding that du disagrees with dust by several TB. Would you have any idea what could be causing the difference?

The commands I am running on the same directory:

sudo du -x -h --max-depth=1 
sudo dust -x -d 1

du agrees with df in regards to the total space used. The difference is something like 4TB of data. I have noticed that dust and du round numbers differently.

[wugeer]

Hi Bootandy,
Thanks for creating and maintaining dust it is excellent piece of software.
I am finding that du disagrees with dust by several TB. Would you have any idea what could be causing the difference?
The commands I am running on the same directory:

sudo du -x -h --max-depth=1 
sudo dust -x -d 1

du agrees with df in regards to the total space used. The difference is something like 4TB of data. I have noticed that dust and du round numbers differently.

You can try adding the -s parameter. :)

[ammaraziz]

The -s results in the total size being greater than what I think the total disk space is. So it went from 25T to 35T.

When I use --apparent-size in du, I get a similar value (what I was expecting).

[wugeer]

Can you try du -s and dust -ok?

I'm a newer, If this doesn't work, could you provide more information to help me reproduce the issue?

[ammaraziz]

Thank you for all your help.

du -s
421557112
dust -ok
421518688

This is on a directory with no external mounted drives.

[ammaraziz]

Here's system info:

Using dust version 1.1.1, du version du (GNU coreutils) 8.25.

architecture is x86_64

[wugeer]

Hello, I think I have roughly identified the issue.
On my local machine, there is a directory that contains symlinks to the files.

The results of running du -a and dust -ok in this directory are inconsistent. du reports a result of 16, while dust -ok reports 0.

The difference is that by default, du considers the size of the symlinked file as 4K, while dust considers the size of the symlinked file as 0.

To calculate the actual size of the symlinked file, you need to add the -L parameter.

For your situation, you can try du -s -L and dust -ok -L to check the results. I hope this helps. @ammaraziz