[issue1597] panic: assertion: parent != NULL in hammer_cursor_removed_node (v2.5.1.187.gc1543-DEV, X86_64)

Matthew Dillon dillon at apollo.backplane.com
Mon Dec 7 18:10:55 PST 2009

:This is a known issue. Matt gave us a patch to fix this:
:Just fetch it and 'git am 0001-HAMMER-Fix-cleanup.patch'  to apply to
:your local checkout and then quickkernel.
:I don't know what's blocking to commit this fix.
:Btw, you can take advantage of Alex's minidump port in HEAD to avoid
:such huge dumps :-)
:Antonio Huete

    There is still a another panic related to searches going past the end
    of the key range (which isn't supposed to be able to happen).  I don't
    know if the patch makes it better or worse, if the patch is the cause
    (I don't think it is), or if there are other consequences to the patch.

    I was holding off the commit while trying to track it down but maybe
    I should just commit that patch and treat the remaining panic as
    a separate issue.

    I do still need new crash dumps for the remaining panic (not the
    parent != NULL panic but the other one... I think it was a key
    comparison panic in the btree iteration / search code).


More information about the Bugs mailing list