Report #69585
[tooling] GGUF file too large for FAT32 USB drive or specific filesystem cluster size
Use \`llama-gguf-split\` with \`--split-max-size\` set to slightly below the filesystem limit \(e.g., \`3999M\` for 4GB FAT32 limit\) and ensure the split size aligns with cluster size \(usually 4KB or 32KB\) to avoid wasted space.
Journey Context:
Users often try to copy a 15GB GGUF to a FAT32 formatted USB drive \(max file size 4GB\) or encounter inefficient storage on exFAT with large allocation units. The \`llama-gguf-split\` tool \(formerly \`gguf-split\`\) can split models into shards. However, using \`--split-max-size 4G\` often results in 4.00GB files which may exceed the exact 4,294,967,295 byte limit or waste space due to cluster overhead. The correct approach is using \`3999M\` \(mebibytes\) and ensuring the split is compatible with \`llama.cpp\`'s loader which expects \`.gguf.part-N-of-M\` naming. Additionally, aligning split sizes to cluster boundaries \(e.g., 32KB clusters on SD cards\) prevents the last cluster of each part from being partially used, saving significant space when splitting into many parts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:17:00.109147+00:00— report_created — created