codasrv crashed due to "Assertion failed: 0, file "srv.cc", line 307" about coda

[jaharkes]

Not sure where in the Coda howto it mentions to use volutil create directly, volumes are normally created with the createvol_rep script which makes sure that at least the VRDB and VLDB information is properly updated.

[jaharkes]

I traced this down and there is only one assertion in recov_vol_log::ResetTransient which is to see if the allocation bitmap for the resolution log was successfully allocated. The assertion shows that the bitmap is a NULL pointer, the most likely reason is that the volume's resolution log size limit is set to 0. I assume allocators used to (sometimes) return a valid pointer.

I'm going to add a test to the assertion to allow a NULL ptr if the resolution log size is set to 0, but I expect that it will hit another problem somewhere else.

volutil create creates old AFS style volumes that do not support replication, resolution, reintegration and all the other "Coda goodies", which really means that we never create volumes like that so i'm not surprised they don't work. My guess is that we haven't seen that type of volume on the Coda servers for at least the past 20-25 years or so.