From 4f94caa1b99f1d55e8ee52604c7175a9501fb3f9 Mon Sep 17 00:00:00 2001 From: Anton Kaliaev Date: Fri, 15 Dec 2017 11:11:21 -0600 Subject: [PATCH] explain what to do in case of truncation [ci skip] --- docs/specification/corruption.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/specification/corruption.rst b/docs/specification/corruption.rst index df2ceea62..33e5ba0b0 100644 --- a/docs/specification/corruption.rst +++ b/docs/specification/corruption.rst @@ -51,7 +51,12 @@ Recovering from data corruption can be hard and time-consuming. Here are two app ./scripts/wal2json/wal2json "$TMHOME/data/cs.wal/wal" > /tmp/corrupted_wal 3. Search for a "CORRUPTED MESSAGE" line. - 4. By looking at the previous message and the message after the corrupted one and looking at the logs, try to rebuild the message. + 4. By looking at the previous message and the message after the corrupted one + and looking at the logs, try to rebuild the message. If the consequent + messages are marked as corrupted too (this may happen if length header + got corrupted or some writes did not make it to the WAL ~ truncation), + then remove all the lines starting from the corrupted one and restart + Tendermint. .. code:: bash