Issues from the FTB Tracker
FTBAuto opened this issue ยท 4 comments
Respectful question on the FTB-Modpack-Issues#7439 ...
As I reported this bug originally on the FTB github, and am hoping to find a solution. When you say "This is the FastAsyncWorldsave issue." ... do you mean that it is similar to the problem being experienced by the gentleman posting in this thread (on this specific github): #97
Because he has linked to a mod that is not currently installed on my server, I just logged into my server tower to check and it's not in the mods folder... https://pastebin.com/MyQZBWwT
I have not tried to individually edit a specific mod in a larger modpack. I notice, you have a .jar in the other thread and no reply from the op. Can you tell me if this .jar needs to be installed both client and server side? And I am assuming, I could make sure I have a backup stored and then try switching out the current ftbbackups2-neoforge-1.21-1.0.28.jar installed on my server and see if yours works?
Would greatly appreciate knowing how to resolve the issue of the standard half hour backups not working properly.
Thanks.
PS: I was not seeing this issue until trying to update from Direwolf20's 1.21 modpack beyond version 1.9.0 (both 1.11.1 and 1.10.0 experienced this issue)... I never added to what the modpack was designed to install. For reference, here is the mods folder for the previous version as it was being run prior to trying to update: https://pastebin.com/8hi5gxYJ
It seems the version of ftbbackups2 did not change, and nor was the specific mod "Fast Async World Save[Forge/Fabric]" installed in 1.9.0 either. I figured I would check what mods were installed when I was not experiencing problems.
Again, any help would be appreciated!
FTBTeam/FTB-Mods-Issues#1498 should be resolved in 1.0.29
https://www.curseforge.com/minecraft/mc-mods/ftb-backups-2/files/all?page=1&pageSize=20&version=1.21
FTBTeam/FTB-Mods-Issues#1212
This would be better handled via some kind of incremental backup solution, a feature request for which already exists.
FTBTeam/FTB-Mods-Issues#1211
A feature request for incremental backups already exists. https://github.com/CreeperHost/FTB-Backups-2/issues/93
FTBTeam/FTB-Mods-Issues#919
Resolved in #74
FTBTeam/FTB-Mods-Issues#539
This looks like a crash related to saving taking too long, likely similar to 919
FTBTeam/FTB-Mods-Issues#319
Another issue that would mostly be resolved by an incremental backup solution.
FTBTeam/FTB-Mods-Issues#95
This isnt really possible with cron based backup scheduling.
FTBTeam/FTB-Mods-Issues#22
This has already been implemented in the form, of the tiered backup retention option.
FTBTeam/FTB-Modpack-Issues#7439
This is the FastAsyncWorldsave issue.
Updated to Direwolf20's 1.21 version 1.12.0 yesterday and all of the server saves seemed to be functioning properly. It don't think ftb-backups changed at all between 1.10.0 and 1.12.0, so I'm not sure why it's working properly again... Still never had the FastAsyncWorldsave mod installed, so not sure why it's looks like it's working properly again.
@poeticwatcher
The root cause of the issue in #97 was the fact that FastAsyncWorldsave was still changing files on disk while FTB backups was in the process of saving.
Normally we avoid this issue by simply tuning off world saving during a backup, but FastAsyncWorldsave, simply due to the way it works, is sometimes still modifying files when we start our backup.
So if you were experiencing the same type of FileNotFound error, then it may have been caused by some other mod changing files.