The following are known minor quirks that have no workaround...
- The 'ls' command cannot represent disk/free sizes for LARGE disks
If you have a file system with more than 4,194,303 blocks (a disk partition
greater that 4 GIG), then the 'ls' numbers for disk size and free size
will NOT be correct. This cannot be fixed, as the number cannot be
represented in a 32 bit 'long' integer.
Since this will not normally happen on Linux (except with NFS mounted
drives), most Linux users will not even notice it. It cannot normally
happen on Linux because the ext2 filesystem will not support partitions
greater than 2 GIG.
- None other at this time.... ;-)