Overlooked line 200 and 201, see comment

line 200 and 201 ensure that the local depth of newly created buckets is
going to be equal to the local depth of the problem bucket, no matter
what we initialize it as. This is correct. So the problem I saw with my
last commit doesn't really apply anymore.

New idea: in p2 the hash works, but we are only using odd numbers there.
The even numbers could be doing something funky and messing it up in p3.

Idea for fixing it without fixing it: Simply do not let the directory
double past a certain point. Not sure if that would work.