Install: Build fails with no space left on exFAT drive despite free space #958
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: needs approval
beanstalk: running
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#958
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported by ℳ. on Discord
What happened
Longshot Launcher 1.0.0 stopped building Nightly 66 (
e51e28e9) while reading game files, at 3%, withOSError: [Errno 28] No space left on device writing romfs/Tex/Wood_Deku_TreeRootProp_E_Nrm.bntx.zs (1859496 bytes): 0.0 GB free there, exFAT. The user reported multiple attempts. Explorer showed 96.7 GB free on the SSD, and switching to a non-exFAT/NTFS drive allowed the build to proceed.Steps to reproduce
Build using an exFAT drive with ample free space. The failure occurred while reading game files; exact setup/reproduction steps are not otherwise known.
System
Windows. Detailed system information was not provided.
Logs and screenshots
Screenshot shows the exact build error and available disk space; a second shows the build progressing after moving to a non-exFAT drive.
Missing information
Please verify whether exFAT is intended to be supported for build output/work files and, if so, reproduce with the launcher/build log and exact drive/build paths. No Windows version, CPU/RAM, or full log was provided.
A related but distinct launcher issue fixed free-space detection at a Windows drive root: Longshot Launcher PR #71. This report concerns an actual
ENOSPCwrite failure on exFAT despite substantial free space shown in Explorer.Files from the Discord report: