Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upPanic in newChunkForEncoding #1243
Comments
This comment has been minimized.
This comment has been minimized.
|
@beorn7 seems like corruption caused by the disk running full. Can we just log and error and delete corrupted chunks as we encounter them? |
This comment has been minimized.
This comment has been minimized.
|
That's exactly what #877 is about. |
beorn7
added
the
duplicate
label
Nov 27, 2015
beorn7
closed this
Nov 27, 2015
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
aecolley commentedNov 27, 2015
I had a prometheus which was crash-looping. On each restart it would complete crash recovery, wait for a minute, and then panic. The error message was always the same.
The host machine also suffered a disk-full condition about a day before, just like in #877 . Or, possibly, prometheus was SIGKILLed while it was still dealing with its SIGTERM. Either way, a write didn't happen, and recovery didn't recover.
Here's a clip of the stderr: