I seem to have 22 Wrong Located chunks in my server world, but when I try to replace them with the region fixer, it replaces 0 chuncks with status "Wrong Location"
It's a 1.8 server btw
Hello!
That is probably because the backups used to replace the wrong located chunks doesn't have those chunks or they are also broken. Have you tried with another backup? Also, when replacing it should print a lot of information with why is not able to replace the chunks.
Please, if you think is a problem in region-fixer, give me some more information.
I am having trouble locating the GUI, can you help me with this?
Hello!
That's because there is not GUI yet! I'm afraid I uploaded the wiki documents thinking I would have the time to finish the gui and upload it but I couldn't finish it! As I always say I will try to upload it as soon as possible. Sorry for the inconvenience.
I'm currently working to fix a really huge world that has many many corrupt chunks, and in trying to fix them I think I found a flaw with your program.
Its running on a Centos 6 Linux with 16G Memory and 6 core AMD processor
I am not a python coder so I am probably wrong, but I'll explain.
We have 2800 region files, and a scan says 2600 have problems, we are trying to fix as much as possible to copy peoples schematics for the new clean world.
When I run the region fixer on just one region that has 444 corrupt chunks, it takes 2 hours. So I started looking at the code.
From looking at it I think as you loop through a region file you read each chunk, if you get an error reading that chunk, the you call the zip routine to delete the chunk. This is where I think the problem is. When you delete a chunk the zip routine rewrites the entire region file skipping the bad chunk.
This means deleting 444 bad chunks will cause that region file to be rewritten 444 times.
If this not what is happening, then why does it take 2 hours to fix 1 region file that is only 4MB
If I am correct, then I think a better way would be to extract all the chunks from the region file skipping the bad ones or replacing them and then to reassemble them all back into a copy region and then rename the region.
I think this would run much faster than single deletes over and over.
But you know your program better, so maybe you can help our slowness problem.
2 other quick questions, your documentation shows a .0.2.0 version, but I cant find that or the qui version, were they ever released ?
and during the del-corrupt process, is it possible to be a little more verbose so we can tell what is happening.
Either way, your program has helped lots of times, so BIG THANKS.
I'm currently working to fix a really huge world that has many many corrupt chunks, and in trying to fix them I think I found a flaw with your program.
Its running on a Centos 6 Linux with 16G Memory and 6 core AMD processor
I am not a python coder so I am probably wrong, but I'll explain.
We have 2800 region files, and a scan says 2600 have problems, we are trying to fix as much as possible to copy peoples schematics for the new clean world.
When I run the region fixer on just one region that has 444 corrupt chunks, it takes 2 hours. So I started looking at the code.
From looking at it I think as you loop through a region file you read each chunk, if you get an error reading that chunk, the you call the zip routine to delete the chunk. This is where I think the problem is. When you delete a chunk the zip routine rewrites the entire region file skipping the bad chunk.
This means deleting 444 bad chunks will cause that region file to be rewritten 444 times.
If this not what is happening, then why does it take 2 hours to fix 1 region file that is only 4MB
If I am correct, then I think a better way would be to extract all the chunks from the region file skipping the bad ones or replacing them and then to reassemble them all back into a copy region and then rename the region.
I think this would run much faster than single deletes over and over.
But you know your program better, so maybe you can help our slowness problem.
2 other quick questions, your documentation shows a .0.2.0 version, but I cant find that or the qui version, were they ever released ?
and during the del-corrupt process, is it possible to be a little more verbose so we can tell what is happening.
Either way, your program has helped lots of times, so BIG THANKS.
Hello!
About the flaw of removing chunks. If it takes 2 hous to remove 444 chunks there is indeed a flaw, or better said, a bug. But that never happened to me before. I have removed hundred of chunks in seconds in my small petty laptop. I'm pretty sure something strange is going in there. Could you hand me one of those broken region files that take that much time to fix?
I don't think the code works as you say but I haven't looked at that code in a lot of time... because I've been working in my (little) free time in the new version. I have uploaded it in github as a new branch called "beta-2". Please, give it a go and tell me if that performs better. And, please, report back with your findings! (that branch also includes the graphic user interface GUI, version).
At the moment, removing chunk can't be more verbose but that is a very good idea and I will add it to my TODO list.
I even copied the file to ram and it still runs slow.
I also download the windows version and tried to run it but I got an error.
elcome to Region Fixer!
(version: 0.1.3)
############################################################
############## Scanning separate region files ##############
############################################################
********** 0 / 1 0% [ ] ETA: --:--:--
*** Error while scanning:
*** r.23.-17.mca
**********
*** Printing the child's Traceback:
*** Exception: <type 'exceptions.OverflowError'> Python int too large to convert
**********
*** File scan.pyc, line 194, in scan_region_file
*** None
**********
*** File scan.pyc, line 278, in scan_chunk
*** None
**********
*** File nbt\region.pyc, line 539, in get_chunk
*** None
**********
*** File nbt\region.pyc, line 520, in get_nbt
*** None
**********
*** File nbt\region.pyc, line 486, in get_blockdata
*** None
**********
Traceback (most recent call last):
File "region-fixer.py", line 304, in <module>
File "region-fixer.py", line 201, in main
File "scan.pyc", line 402, in scan_regionset
scan.ChildProcessException
Hopefully you can learn something from the region file.
I also tried the qui, it looks really nice +10
It lacks one thing, I couldn't figure out how to check just one region file. It seems to just want to check a whole world directory.
I even copied the file to ram and it still runs slow.
I also download the windows version and tried to run it but I got an error.
Hopefully you can learn something from the region file.
I also tried the qui, it looks really nice +10
It lacks one thing, I couldn't figure out how to check just one region file. It seems to just want to check a whole world directory.
Thanks
You have indeed discovered a new bug in regionfixer (more exactly in the nbt library). I have uploaded a new branch "beta-2-1" that fixes the bug. After the fix, it took in my computer 8 seconds to remove all the chunks in that region file. Thanks for reporting!
The error in the windows version is because it is made in python 32 bits and it seems that hit the 32 bits ram limit.
I'm really glad you liked the gui! There is no way to scan a single region file in the gui at the moment. For now it's focused to be simpler than the command line application.
Please, if you have the time, try the new beta version and tell me if that works faster.
Sorry for the delay, I had car problems I had to take care of.
So, I ran the beta-2-1 and it fixed the problems, but it had a few problems.
First I ran a check on the world, it checked 140 map.dat files and after 139 it paused for a long time, it did 139 in seconds, and 5 to 10 minutes on the last one but it eventually continued on to the region files.
When checking 2800 region files it would get to the last one and crash, I had it send several crashes to the ftp site. I believe it fixes the last chunk, and then tries to print the report and thats where it might be crashing.
Then I did the --delete-corrupt and that fixed the chunks, but and it would get to the last one, pause for a while and then crash again.
Fixing all the chunks took about two hours, but that was alot faster then running it seven hours and hardly putting a dent in the broken ones.
Thanks, for helping get our chunks fixed. I'm willing to do any testing or give you and data/region files that you might need to help you get the program working. Just let me know what you need and I'll get it for you.
Sorry for the delay, I had car problems I had to take care of.
So, I ran the beta-2-1 and it fixed the problems, but it had a few problems.
First I ran a check on the world, it checked 140 map.dat files and after 139 it paused for a long time, it did 139 in seconds, and 5 to 10 minutes on the last one but it eventually continued on to the region files.
When checking 2800 region files it would get to the last one and crash, I had it send several crashes to the ftp site. I believe it fixes the last chunk, and then tries to print the report and thats where it might be crashing.
Then I did the --delete-corrupt and that fixed the chunks, but and it would get to the last one, pause for a while and then crash again.
Fixing all the chunks took about two hours, but that was alot faster then running it seven hours and hardly putting a dent in the broken ones.
Thanks, for helping get our chunks fixed. I'm willing to do any testing or give you and data/region files that you might need to help you get the program working. Just let me know what you need and I'll get it for you.
Thanks
Hello!
The map issues also happen to me in my test worlds. I don't think it's a problem, theres one of the data files that is pretty big compared to the others (Minecshaft.dat) and I think it takes more time to scan.
About the crash after ending the scan... yep! That is becuase is trying to print the summary of all problems found but there is a error in that part of the code. Also, all the auto bug reports were received properly! So you also tested the auto bug report sending thinghy, thanks! I've got the summary printing error almost fixed. I will fix it and push it as soon as I get some free time. If you want I can tell you when I push the new beta (through here).
I'm glad it took less time to fix all those chunks... it seems you world it's really corrupted! If it's not a problem for you, could I have a copy of your world? If it is too big to upload or too much to ask for, could I have a copy of the worst region files (most broken) in your world? I'm always trying to get new stuff to test region-fixer.
Well the world compressed is 6GB, so I think that would be too much, and the funny thing is, your program fixed everything, So I had to search through the backups to find the bad stuff. lol
So I got you all the bad or wrong regions which were only 6 region files. And some other data files.
I have a suggestion, when I run the fixer with -v it prints out a line for every region file checked, and out of 2800 only 12 had problems,
is it possible to only print a line with just the bad regions listed ? It has always listed so much output, that I never really checked to see how many regions files were bad.
Something like this would have helped
unk problems:
-------------------------------------------------------------------
| Problem | Corrupted Wrong l. Etities Shared o. Total chunks |
-------------------------------------------------------------------
| Counts | 1201 3211 0 0 2805964 |
-------------------------------------------------------------------
Well the world compressed is 6GB, so I think that would be too much, and the funny thing is, your program fixed everything, So I had to search through the backups to find the bad stuff. lol
So I got you all the bad or wrong regions which were only 6 region files. And some other data files.
I have a suggestion, when I run the fixer with -v it prints out a line for every region file checked, and out of 2800 only 12 had problems,
is it possible to only print a line with just the bad regions listed ? It has always listed so much output, that I never really checked to see how many regions files were bad.
Something like this would have helped
Happy hunting
Thanks
Thanks for all! You can use --log option to do that! Just do 'regionfixer.py --log bad_regions.log world/to/scan' and it will save a log file with in detail information of broken files. As the --help says:
Saves a log of all the problems found in the spicifyed
file. The log file contains all the problems found
with this information: region file, chunk coordinates
and problem. Use '-' as name to show the log at the
end of the scan.
Hi, I have a 1.7.10 chunk corrupted world with UUIDs on it... will this be able to work on it
Hey. I don't know what really mean a corrupted chunk with uuids (I think those are pretty different things). Anyway, it should work to scan a corrupted chunk in 1.7, but if you want to scan a few player UUIDs files you need to try the beta:
Hello, could you please kindly let me know if this version or any beta version is compatible with Spigot 1.8? Thank you!
Hello!
I kindly let you know that the las stable and the last beta version should work with minecraft 1.8 in any of its forms. But please, always remember to make a backup before running region-fixer!
The beta is better if you are lucky and don't find any crashing/hanging bug.
HI! The Windows.exe file in Mediafire is no longer able to download... Could the OP either update it or could somebody else who downloaded it post a copy somewhere? Thanks!
Hello!
That is probably because the backups used to replace the wrong located chunks doesn't have those chunks or they are also broken. Have you tried with another backup? Also, when replacing it should print a lot of information with why is not able to replace the chunks.
Please, if you think is a problem in region-fixer, give me some more information.
Hello!
That's because there is not GUI yet! I'm afraid I uploaded the wiki documents thinking I would have the time to finish the gui and upload it but I couldn't finish it! As I always say I will try to upload it as soon as possible. Sorry for the inconvenience.
I'm currently working to fix a really huge world that has many many corrupt chunks, and in trying to fix them I think I found a flaw with your program.
Its running on a Centos 6 Linux with 16G Memory and 6 core AMD processor
I am not a python coder so I am probably wrong, but I'll explain.
We have 2800 region files, and a scan says 2600 have problems, we are trying to fix as much as possible to copy peoples schematics for the new clean world.
When I run the region fixer on just one region that has 444 corrupt chunks, it takes 2 hours. So I started looking at the code.
From looking at it I think as you loop through a region file you read each chunk, if you get an error reading that chunk, the you call the zip routine to delete the chunk. This is where I think the problem is. When you delete a chunk the zip routine rewrites the entire region file skipping the bad chunk.
This means deleting 444 bad chunks will cause that region file to be rewritten 444 times.
If this not what is happening, then why does it take 2 hours to fix 1 region file that is only 4MB
If I am correct, then I think a better way would be to extract all the chunks from the region file skipping the bad ones or replacing them and then to reassemble them all back into a copy region and then rename the region.
I think this would run much faster than single deletes over and over.
But you know your program better, so maybe you can help our slowness problem.
2 other quick questions, your documentation shows a .0.2.0 version, but I cant find that or the qui version, were they ever released ?
and during the del-corrupt process, is it possible to be a little more verbose so we can tell what is happening.
Either way, your program has helped lots of times, so BIG THANKS.
Hello!
About the flaw of removing chunks. If it takes 2 hous to remove 444 chunks there is indeed a flaw, or better said, a bug. But that never happened to me before. I have removed hundred of chunks in seconds in my small petty laptop. I'm pretty sure something strange is going in there. Could you hand me one of those broken region files that take that much time to fix?
I don't think the code works as you say but I haven't looked at that code in a lot of time... because I've been working in my (little) free time in the new version. I have uploaded it in github as a new branch called "beta-2". Please, give it a go and tell me if that performs better. And, please, report back with your findings! (that branch also includes the graphic user interface GUI, version).
At the moment, removing chunk can't be more verbose but that is a very good idea and I will add it to my TODO list.
Hope that helps!
Here is the region file http://cardinalcraft.net/drop/r.23.-17.mca
it has 782 corrupted chunks out of 1024
No luck on beta-2, it still runs real slow.
I even copied the file to ram and it still runs slow.
I also download the windows version and tried to run it but I got an error.
Hopefully you can learn something from the region file.
I also tried the qui, it looks really nice +10
It lacks one thing, I couldn't figure out how to check just one region file. It seems to just want to check a whole world directory.
Thanks
You have indeed discovered a new bug in regionfixer (more exactly in the nbt library). I have uploaded a new branch "beta-2-1" that fixes the bug. After the fix, it took in my computer 8 seconds to remove all the chunks in that region file. Thanks for reporting!
The error in the windows version is because it is made in python 32 bits and it seems that hit the 32 bits ram limit.
I'm really glad you liked the gui! There is no way to scan a single region file in the gui at the moment. For now it's focused to be simpler than the command line application.
Please, if you have the time, try the new beta version and tell me if that works faster.
Good luck!
So, I ran the beta-2-1 and it fixed the problems, but it had a few problems.
First I ran a check on the world, it checked 140 map.dat files and after 139 it paused for a long time, it did 139 in seconds, and 5 to 10 minutes on the last one but it eventually continued on to the region files.
When checking 2800 region files it would get to the last one and crash, I had it send several crashes to the ftp site. I believe it fixes the last chunk, and then tries to print the report and thats where it might be crashing.
Then I did the --delete-corrupt and that fixed the chunks, but and it would get to the last one, pause for a while and then crash again.
Fixing all the chunks took about two hours, but that was alot faster then running it seven hours and hardly putting a dent in the broken ones.
Thanks, for helping get our chunks fixed. I'm willing to do any testing or give you and data/region files that you might need to help you get the program working. Just let me know what you need and I'll get it for you.
Thanks
Hello!
The map issues also happen to me in my test worlds. I don't think it's a problem, theres one of the data files that is pretty big compared to the others (Minecshaft.dat) and I think it takes more time to scan.
About the crash after ending the scan... yep! That is becuase is trying to print the summary of all problems found but there is a error in that part of the code. Also, all the auto bug reports were received properly! So you also tested the auto bug report sending thinghy, thanks! I've got the summary printing error almost fixed. I will fix it and push it as soon as I get some free time. If you want I can tell you when I push the new beta (through here).
I'm glad it took less time to fix all those chunks... it seems you world it's really corrupted! If it's not a problem for you, could I have a copy of your world? If it is too big to upload or too much to ask for, could I have a copy of the worst region files (most broken) in your world? I'm always trying to get new stuff to test region-fixer.
Thanks for the testing!
So I got you all the bad or wrong regions which were only 6 region files. And some other data files.
Here is the link http://cardinalcraft.net/drop/world.tar.gz
I have a suggestion, when I run the fixer with -v it prints out a line for every region file checked, and out of 2800 only 12 had problems,
is it possible to only print a line with just the bad regions listed ? It has always listed so much output, that I never really checked to see how many regions files were bad.
Something like this would have helped
Happy hunting
Thanks
Thanks for all! You can use --log option to do that! Just do 'regionfixer.py --log bad_regions.log world/to/scan' and it will save a log file with in detail information of broken files. As the --help says:
Saves a log of all the problems found in the spicifyed
file. The log file contains all the problems found
with this information: region file, chunk coordinates
and problem. Use '-' as name to show the log at the
end of the scan.
Thanks!
Yes, it works in 1.8. Also, if you are brave enough you can test the beta:
https://github.com/Fenixin/Minecraft-Region-Fixer/tree/beta-2-1
Hey. I don't know what really mean a corrupted chunk with uuids (I think those are pretty different things). Anyway, it should work to scan a corrupted chunk in 1.7, but if you want to scan a few player UUIDs files you need to try the beta:
https://github.com/Fenixin/Minecraft-Region-Fixer/tree/beta-2-1
Good luck everyone!
Hello!
I kindly let you know that the las stable and the last beta version should work with minecraft 1.8 in any of its forms. But please, always remember to make a backup before running region-fixer!
The beta is better if you are lucky and don't find any crashing/hanging bug.
Yep! That is its purpose. But it depends a lot on what you mean with "fix" and "corrupted". Ask if you need more info.
Op here, the link works for me. What is exactly the problem?
New version out! (0.2.0)
It has a flashy GUI for all you and some new cool features as:
It took mucho more than expected, but life is busy!