Alan Cox wrote:
tracking a lot of hard links, it might be using a lot of memory -- I'd
think it would have to store the inode number for each multi-linked file.
I don't know what it does with hard-linked directories (but don't use
hard-linked directories!).
Compare the performance to a "find . -size 1024" >/dev/null
The find is fetching as much inode and name space data but shouldn't be
doing any link work.
I just tried this on the same 3TB volume as the du and I get almost
identical results, ~90 minutes.
--
Ita erat quando hic adveni.
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
