<div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 2 Jun 2020 at 12:10, Fairlight via Filepro-list <<a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">It's the result of bad BTree+ code.<br>
<br>
If you go through this demo, you'll see when data needs to be split.<br>
Something about it is incorrectly handled in fP, resulting in bad<br>
indexes.<br>
<br>
<a href="https://www.cs.usfca.edu/~galles/visualization/BPlusTree.html" rel="noreferrer" target="_blank">https://www.cs.usfca.edu/~galles/visualization/BPlusTree.html</a><br><br></blockquote><div><br></div><div>I got lucky and found that the nightly tar archive had the troubled data.</div><div>I was able to play around with it on a test system and found I could get a DKNF (deleted key not found) error on the data in addition to the sanity check</div><div>The data is part of a simple routine that is created and used in a single process ... so it easily traceable.</div><div><br></div><div>All lookups involved in record operations (creating, deleting, modifying) are protected (-p flag) lookups. </div><div>Each record operations concludes with a write - 'write [lookupname''. Create a record; write that record. Delete a record; write that record. etc.</div><div>The routine concludes with a 'sync'.</div><div><br></div><div>So I can't think of anything that I've missed to cause invalid key/index issues.</div><div>Did I miss something?</div><div><br></div><div><br></div></div></div>