MO2 does not handle disk full situation

[katzmannr]

The problem:

I have a Skyrim SE profile with around 250 mods (Portable Instance).
I had it running in Debug mode to check if a plugin was working correctly (it worked).
One day later the log file was grown so much that my drive was full (my fault).
MO2 tried to save it's profile on that full drive while creating log.
This effectively destroyed the profile.

To Reproduce:

Steps to reproduce the behavior:

1. Create Minimal Profile (Game should not matter)
2. Make sure disk is nearly full
3. Let log files fill the drive to 100% (I guess debug mode accelerates this)
4. Make a change in profile that updates it (like activate mod or activate plugin or change load order)

Environment:

• Mod Organizer Version that exhibits the issue: 2.5.2
• Last Mod Organizer Version that did not exhibit the issue (if applicable): n/a
• Desktop OS/version used to run Mod Organizer: n/a (does not matter, happens on any Windows version, or in Virtual Machine or other environment)

Details:

Link to Mod Organizer logs:

Log file too big to append and meanwhile deleted. Can be recreated if needed,.

USVFS:

This is not related to USVFS

MO Interface:

This is not a UI problem.

Expected Behavior:
MO2 checks result from file I/O operations, so that at least not more than one file is damages instead of all 5 files in the profile (archives.txt, loadorder.txt, modlist.txt, pluginsgroups.txt, plugins.txt). A disk full message would wake up the user to check his disk.