Commit 11858d5b authored by Jim Fulton's avatar Jim Fulton

Somehow, someone got a zero previous record pointer on a record for an

object that has previous records.  This caused a panic on startup
because the previous record pointer did not agree with the system's
knowledge that there was, indeed, a previous record. This is a
pretty benign situation, so, I've changed the check to log a warning
of the previous record pointer is zero and there is a previous record.
parent b7829e0e
No related merge requests found
......@@ -184,7 +184,7 @@
# may have a back pointer to a version record or to a non-version
# record.
#
__version__='$Revision: 1.28 $'[11:-2]
__version__='$Revision: 1.29 $'[11:-2]
import struct, time, os, bpthread, string, base64, sys
from struct import pack, unpack
......@@ -1323,8 +1323,10 @@ def read_index(file, name, index, vindex, tindex, stop='\377'*8,
panic("%s data record exceeds transaction record at %s",
name, pos)
if index_get(oid,0) != prev:
panic("%s incorrect previous pointer at %s",
name, pos)
if prev:
panic("%s incorrect previous pointer at %s", name, pos)
else:
warn("%s incorrect previous pointer at %s", name, pos)
pos=pos+dlen
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment