1.7.7: upper limit to df reported available size?

Eric Blake eblake@redhat.com
Fri Dec 10 17:38:00 GMT 2010

On 12/10/2010 10:21 AM, Corinna Vinschen wrote:
> On Dec 10 17:59, Corinna Vinschen wrote:
>> On Dec 10 11:20, Elford,Andrew [Ontario] wrote:
>>> $ df -T /cygdrive/f/file
>>> Filesystem    Type   1K-blocks      Used Available Use% Mounted on
>>> C:            ntfs    83886076  31717608  52168468  38% /cygdrive/c
>>> F:            ntfs   11717703676  72036296 -5534201804   -  /cygdrive/f
>>> L:            ntfs   6143999996 883063196 5260936800  15% /cygdrive/l
>> [...]
>> Hmm.  OTOH, seeing the size of your FS, I'm also wondering if we should
>> make the algorithm a bit more foolproof for the future by manipulating
>> the value of f_frsize if the TotalAllocationUnits returned by Windows
>> is > sizeof (fsblkcnt_t).
> No, scratch that.  It wouldn't work well.  I guess what we really need
> is to redefine fsblkcnt_t to become a 64 bit type.  Oh well, this
> requires another backward compatibility hack, just like back when we
> switched to 64 bit off_t (Cygwin 1.5).

Let's do it at the same time as we change sigset_t and time_t to 64-bits
(with knock-on effects to struct stat, among others).  In other words,
all good changes, but certainly something that will take a lot of
planning to pull off in one go.

Eric Blake   eblake@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 619 bytes
Desc: OpenPGP digital signature
URL: <http://cygwin.com/pipermail/cygwin/attachments/20101210/5a653b37/attachment.sig>

More information about the Cygwin mailing list