Yes, as the title said, the filesystem is fulled up. To be honest I just think there should be a mechanism to stop writing new blocks and force quit the server, or whatsoever solution, to prevent such corrupted maps. I am horrified every time ever since this bug came up, the error fears me that someday the map will go south.
Also I think a repair mechanism to existing corrupted maps should be implemented as well. :3
Can confirm on MC 1.13.2 too.
The error message are similar to ones previously reported:
[02:33:36 ERROR]: Error loading saved data: villages
java.io.EOFException: null
...
[02:33:36 ERROR]: Error loading saved data: villages_nether
java.io.EOFException: null
...
[02:33:36 ERROR]: Error loading saved data: villages_nether
java.io.EOFException: null
...
[02:33:36 ERROR]: Error loading saved data: villages_end
java.io.EOFException: null
...
[02:33:36 ERROR]: Error loading saved data: villages_end
java.io.EOFException: null
Thanks for your comment but please don't judge a book by it's cover, we run our production services on rack servers in datacenters and other colocation sites, and all our disk arrays and SAN are saturated because of map saves and player data. By no means we would just stuff the server that full, only if knowing how Minecraft is so fragile like you said.