how does "du" deal with hard links?
Luciano Rocha
strange at nsk.no-ip.org
Thu Nov 1 14:41:09 UTC 2007
On Thu, Nov 01, 2007 at 08:47:43AM -0400, Robert P. J. Day wrote:
> $ du -s git*
> 26340 git
> 9672 git.local
> 26292 git.nolinks
> $
>
> as if du already knows which files it's seen under "git" and won't
> recount them under "git.local" based on hard links. if that's the
> case,
Yes, du skips files with the same inode.
> then it won't be surprising to see the numbers on the first two
> reversed if i explicitly change the order of the arguments:
Yes, unless their contents are exactly the same.
> $ du -s git.local git git.nolinks
> 26292 git.local
> 9720 git
> 26292 git.nolinks
> $
>
> i can see what's happening, i just didn't realize that that's how
> "du" operated. is that deliberate?
>
26340+9672 = 26292+9720 = 36012
Files in git.local but not in git:
9672
Files in git but not in git.local:
9720
Files common in git.local:
26292-9672 = 16620
Files common in git:
26340-9720 = 16620
--
lfr
0/0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20071101/b9bdb20f/attachment-0001.bin
More information about the users
mailing list