OK, did that, and going over 32 GB is no problem. The test big_file_test ran with no errors.
In Windows Subsystem for Linux, before big_file_test run:
carlk@Dell:/mnt/g$ du -c -h *
0 System Volume Information/ClientRecoveryPasswordRotation
0 System Volume Information/AadRecoveryPasswordDelete
64K System Volume Information
3.0G big1
992K big1MB
27G hog
31G total
carlk@Dell:~$ df -h /mnt/g
Filesystem Size Used Avail Use% Mounted on
G: 120G 31G 90G 26% /mnt/g
In Windows Subsystem for Linux, after big_file_test run:
carlk@Dell:/mnt/g$ du -c -h *
0 System Volume Information/ClientRecoveryPasswordRotation
0 System Volume Information/AadRecoveryPasswordDelete
64K System Volume Information
3.0G big1
992K big1MB
3.0G big2
27G hog
34G total
carlk@Dell:/mnt/g$ df -h /mnt/g
Filesystem Size Used Avail Use% Mounted on
G: 120G 34G 87G 28% /mnt/g
Windows Command Prompt:
C:\Users\carlk>chkdsk g:
The type of the file system is FAT32.
Volume THE 128GB created 3/16/2020 11:49 AM
Volume Serial Number is 1315-2346
Windows is verifying files and folders...
File and folder verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
124,821,728 KB total disk space.
64 KB in 2 hidden files.
96 KB in 3 folders.
34,604,064 KB in 14 files.
90,217,472 KB are available.
32,768 bytes in each allocation unit.
3,900,679 total allocation units on disk.
2,819,296 allocation units available on disk.
Next, I will try straddling the 64 GB boundary.
BTW, is what I’m doing in big_file_test.c grossly inefficient, or is this kind of test just going to take a long time? I currently have ffconfigCACHE_WRITE_THROUGH 1 and xIOManagerCacheSize = 4 * SECTOR_SIZE (i.e., 2 kB).