Having a bigger File Allocation Size had its advantages and disadvantages:
- Less disk space usage on Large Files
- Fast read times
- It consume 2x or 3x disc space on smaller files
* The correct example of this case is "Atelier Meruru" game that is only 2.8GB game but it consumes nearly 4GB of space on FAT32 HDD. This is because that most of the files (3k+ files are less than 256byte which breaks the 32k and 64kbyte cluster size. Each cluster can only store 1 file information, any files is smaller than 32kbyte are will be stored on a single cluster and the remaining space will be consumed, even if that space is empty or null.) are to small that it needs to store every file in individual cluster.
- Slow seek times on files that is stored on a single cluster (file indexing is not implemented on FAT32, NTFS it is) so sometimes you have to wait much longer unlike when you play it using BD disc.
* Correct example is "Naughty Bear" game.
On most cases: you should keep your self on 32kbyte cluster size, to avoid problems.
Model: CECHC04 PAL/EUR 60GB SKU Console
Firmware: REBUG 3.55 CFW [DEBUG MODE, DEBUG XMB, MENU OPTION 2]
BM: Iris Manager v1.2 (Hermes Syscall8)