Homebrew Question Any progress on safely playing PS1 emulators on ExFat?

[HoTsHoTz79]

Thanks! What did you use for files bigger than 4gb?

thats what i was worried about when trying to transfer back... only to realize that even if the NSP was original 10GB or whatever... the installed NSP files are all under 4GB

(unless ofcourse you are storing single file over 4GB... that wouldn't transfer to FAT32)

 

[Rob Blou]

thats what i was worried about when trying to transfer back... only to realize that even if the NSP was original 10GB or whatever... the installed NSP files are all under 4GB

(unless ofcourse you are storing single file over 4GB... that wouldn't transfer to FAT32)

Yeah the thing is I still use XCI a lot :S

 

[smf]

The reason for that is FAT32 supports journaling and exFAT doesnt. (see: https://superuser.com/questions/638...need-repair-whenever-i-accidentally-unplug-it )


So the takeaway is still to use fat32 for all your daily use scenarios.

FAT32 doesn't support journalling. exFAT is designed to reduce unnecessary writes, it appears that the crappy way that software is running on the switch at the moment means that data is not being flushed when you close the app. Once we move away from hacking into the photo album then it will become way more stable (or maybe someone can add a further patch that causes everything to be shut down properly)

 

[notimp]

Thank you for the correction. Then it makes even less sense why exfat would corrupt "more", but apparently it does. (If anyone has an explanation, please share. )

I've read a bugtracker discussion a few months back, where people indicated, that even shutting down the Switch while a write onto the sdcard in exfat was ongoing would corrupt the filesystem - so in that sense it wouldnt be specific to the gallery hack. The conclusion drawn there was, that it was Nintendos exfat implementation, or maybe exfat on its own, that were to blame.

We also already have the possibility to inject the loaders at nsp launch, no information on how this affected file system integrity on crashes on exfat.

What retroarch seemingly implemented right now is an interrupt of the home button call, so the apps wouldnt crash, but rather have you exiting them cleanly to exit them at all.

All in all we are now at even more "hearsay" than we started with. And all I can say is, that I've been on fat32 since the beginning and never experienced any file system issues whatsowever.

And I've certainly exited RA via the home button by mistake before. (Maybe not during diskwrites, who knows..)

 

[smf]

Thank you for the correction. Then it makes even less sense why exfat would corrupt "more", but apparently it does. (If anyone has an explanation, please share. )

exfat is designed for sustained write speed, so you don't keep updating all the meta data & the way free space is managed is different.

I'm not sure why the app closing should have any effect, it's weird that the file system would actually care about an application closing. So in that respect it's a weird design choice. It's possible that the homebrew sdk is missing some calls that would prevent the app from being closed or make sure the data is written.

I use exfat and I've never had a corruption, but then I will never run RA.

 

[mranonymous]

Even if you call your harddrive a backup drive, something that exists only once isn't a backup. Its the thing. Yes, you can transfer your "backup" over to an sdcard again if needed. There are also tools to restore the backup from a PC, over usb - if needed.

Okay nice, thanks. And right, I meant I have the Backup stored on my computer, and also on my backup drive as a second instance.