If you’re using this among Macs, reformat and use HFS+ or APFS, and not FAT.
As for FAT, that is poorly designed and flaky, with differing block sizes which lead to differing addressing limits, too.
I don’t recall the details of the FAT addressing limits offhand, but do recall discovering FAT32 was really rather closer to FAT28 as it was implemented.
Long with legal encumbrances from Microsoft too, encumbrances that lead to many differing interpretations, and with no reference standard or tests, and which in aggregate led to bugs. If it glitches, reformat it. If it glitches in one particular device, use that same device to reformat it. Or better, rework the data transfer process to eliminate use of FAT, or of sneakernet.
Microsoft relented and published some FAT specs in 2019, but diverging and incompatible FAT implementations will exist for the foreseeable future.
Some general background: https://en.wikipedia.org/wiki/File_Allocation_Table
TL;DR: erase and reformat as FAT and test again, or reformat as HFS+ or APFS if solely used with Apple gear, or eliminate its use entirely is feasible.