Re: du(1)/fts(3) integer overflow

In message: <[EMAIL PROTECTED]> Peter Jeremy <[EMAIL PROTECTED]> writes: : For 6.x, the ABI isn't fixed so fts_number can be changed to int64_t. We have to be careful how we deal with these things... You do not have license to break libc ABI, even in current, without careful considera

Re: du(1)/fts(3) integer overflow

On Mon, 2004-Dec-13 11:42:17 -, henry wrote: >I have noticed a problem with the fts(3) library or the way du(1) interacts >with it. > >A 3.2TiB file gives the following output: >> du -cs /fs/file >3408720016 /fs/file >-886247279 total > >This is because while stat(2) reports blocks as

du(1)/fts(3) integer overflow

I have noticed a problem with the fts(3) library or the way du(1) interacts with it. A 3.2TiB file gives the following output: > du -cs /fs/file 3408720016 /fs/file -886247279 total > du -hcs /fs/file 3.2T/fs/file total > This is because while stat(2) reports blocks as a 64