I have a batch script in which I need to make sure I have at least 3 GB of available free space.
To get the available free space via command line you type:
fsutil volume diskfree C: | find /i "avail free"
Total # of avail free bytes : 872762081280
This is the number of bytes, which is similarly displayed when you 'right click' -> 'property' on your C drive.
However, when I 'right click' -> 'property' on my C drive, next to the 872,762,081,280 it shows me a GB value of only 812GB of available free space. This is drastically different from the byte value of 872762081280.
I thought this might be due to the 1024bytes = 1kb windows conversion. However, this conversion will show i have 852,306,720kb available (or 852GB) which is still not close to the 812GB which the 'Local Disk (C:) Properties' window is showing me.
Does anyone know the math which windows is using which converts 872,762,081,280 bytes down to 812GB?
There are 1024 bytes in a KB, 1024 KB in a MB, 1024 MB in a GB so:
Note the use of KB, MB, and GB follow the JEDEC memory standards nomenclature
Under IEC 60027 notation these would be denoted by KiB, MiB and GiB
There is much confusion over this since they both use multiples of 1024, but the Decimal nomenclature uses the same KB, MB and GB but with multiples of 1000, as used by some disk manufacturers