clb92

Members
  • Posts

    32
  • Joined

  • Last visited

Posts posted by clb92

  1. Just now, binhex said:

    it sounds like some sort of corruption, or perhaps its the location you are saving to, is it unassigned devices?, cache pool?, array?, the issue may even be file system corruption.

    A single-SSD cache pool (been running the Minecraft server on there for about a year). I'll let you know if I find anything.
    Thanks for maintaining all these containers, by the way!

  2. 1 minute ago, binhex said:

    not at present, no, i could change this but it could fill your disk fairly quickly if you are backing up that frequently, but i can understand you not wanting to loose any changes, im perplexed as to why its happening to be honest.

    I plan on testing with a new Minecraft world, and maybe even with completely new reset /config folder too, once I get some more free time. Maybe it could be some sort of corruption in the world files, but who knows...

  3. 18 minutes ago, binhex said:

    hmm ok that shouldnt be happening then. ok investigation on this is going to be tricky for me, as i dont have a copy of minecraft java, for now one thing you can do to mitigate this is to use the backup feature i built into this container, for instance setting the values as follows will get you very frequent backups of your world, 1 every hour with a purge of the backups every 7 days, change to fit to what you want.

    
    CREATE_BACKUP_HOURS=1
    PURGE_BACKUP_DAYS=7

     

    Is it possible to back up more often than every hour?

     

  4. 6 hours ago, binhex said:

    how long after creating the change in the world are you shutting down the container?, if its less than 5 minutes then there is a chance your change will be lost, as this is the time set for changes to be committed to the world (hard set my mojang i think).

    At least 3-4 hours.

  5. I'm having a very annoying issue. Started a week or two ago, I think. When I stop the docker container, the Minecraft world isn't saving all changes. Inventories and chests are saved as expected, but I just lost a like 1500 block long tunnel, twice. I thought the first "rollback" was a fluke, so I spent a couple of hours redoing it, just to find everything gone again after restarting the container.

     

    I've been doing some quick testing, and if I specifically go into the console and type 

    stop

    to stop the server, it saves the world as expected, but doesn't stop the container. After then stopping the container manually and starting it again, the world loads with all recent changes saved as expected.

     

    Is it because just stopping the container for some reason doesn't stop the server gracefully? Surely the minecraft server should auto-save the world once every few minutes anyway, right?

     

    There doesn't seem to be anything out of the ordinary in the container log, or printed in the server console.

     

    Any ideas?

  6. 4 minutes ago, trurl said:

    Post your docker run command as explained at the first link in the Docker FAQ pinned near the top of the Docker Engine subforum. 

    Sorry.

    I just realized that it's because the template changed, so it added some new default path to the container when I clicked update. And apparently Unraid just automatically creates new shares if a new folder is created in /mnt/user it seems. No help needed anyway.