Closed KevinX8 closed 2 years ago
Yeah this isn't really an atmosphere bug, but delete your reports.
(this is a FAT filesystem limitation)
seeing as exFAT is not recommended to be used for homebrew would it not make more sense for atmosphere to automatically delete reports when there are too many of them instead of just crashing?
This has nothing to do with exFAT, and "delete" if the folder is in that state, accessing it gives an error, we can't delete from that state.
Some erpt report cleanup can be considered, for sure, but in the meantime "just delete your reports".
yes, I have deleted them, which means it is possible to delete the reports, from some brief research online the max files fat32 can have in a folder is around 65k, which 16k is nowhere near that, and also atmos could wipe the reports let's say 1k reports before the crash loop begins no so that the access problem is not a thing?
"accessing gives it an error" -> using the switch's FS driver :P
"accessing gives it an error" -> using the switch's FS driver :P
I understand the switch could be incapable of deleting it when the problem already began yes, which is why I suggested a preventive measure and deleting the logs when you're around 10% away from the bug occurring
Some erpt report cleanup can be considered, for sure, but in the meantime "just delete your reports".
Does the above actually resolve your error?
I would guess so yes, I would have to accumulate the amount of logs needed to cause the crash to test this functionality which would take an extremely long time
Bug Report
What's the issue you encountered?
My atmosphere\erpt_reports folder contained 16383 reports just from normal usage over a few years and my switch would constantly crash on boot with error 2002-0039. I made no changes to atmosphere.
How can the issue be reproduced?
Use the switch normally for about 2 years or just fill the erpt_reports folder with as many reports as you can until you get into the crash loop.
Crash Report
I deleted the crash reports in order to be able to boot my system again.
System Firmware Version
13.2.0
Environment?
Additional context?