Number of files limit on FAT32

ivntvrs

Hello my friends, i facing a problem with the image that i making, actually the image have 279.782GB i trying to add some more things but the Windows return the following error:

https://imgur.com/Y00ik0F

I was searching about and find this:

FAT32:
Maximum number of files: 268,435,437
Maximum file size: 4GB
Maximum number of files per directory: up to 65535, or less depending on file names
NTFS:
Maximum number of files: 4,294,967,295
Maximum file size: 16TB currently (16EB theoretically)

Knowing this i think que troublemaker was the "Maximum number of files per directory" so i list the files and the result was: 21.871 Files (But considering the filename length the guilty was found )

I make the test and i cant copy any file to the folder "G:\roms\mame\downloaded_images\"
but for example if i try to copy the same file to the folder "G:\roms\mame\" copy normally

I even try to copy using the ROBOCOPY but same result, log above:
http://s000.tinyupload.com/index.php?file_id=00384478038851014730

Anyone know how to solve or at least work around this problem, i want to copy this missing snapshots haha.

Thanks in advance.

nadenislamarre

fat32 (1996) and ntfs (1993) are old filesystems. Unfortunaltly windows didn't evolve technically about theses points. For batocera,i recommand to use ext4 (2008) which handles really better big files (big roms), have limitations that fits the today requirements and that doesn't require defragmentation (like most of modern filesystems). The only drawback is that it's not supported on windows. But nothing good in term of filesystem is supported by windows nowadays.

ivntvrs

I appreciate the suggest and now i using ext4 with no problems, and i never considered the defrag problem, thanks men.

nadenislamarre

note that defragmentation is not really a problem on batocera while files are copied once, not moved all the time.
note that an other alternative is exfat eventually. it is supported by windows. it has however the problem like the fat that it can be corrupted in case the system (batocera is our case) is not shut down correctly (fsck may be required). It's done for camera, and big files, but it's not a robust filesystem because it targets simplicity (embeded devices) and space against robustess and complexity