Well, it's not hard to reproduce, but the real issue here is that
we have an assert on contents of bh->b_data we'd just read from
disk. This is the first time we are looking at the entries->limit
and if it's corrupt on-disk the assert will trigger, of course.
IOW, it's a bullshit test in bull^Wdaniel's code. Proper reaction
is to give a warning and bail out as it's done for tests just above.