On Sun Jun 21 07:59:52 EDT 2009, 9f...@hamnavoe.com wrote: > > Forgot to add that I've only seen one error on the console during all of > > this: > > /boot/fossil: could not write super block; waiting 10 seconds > > /boot/fossil: blistAlloc: called on clean block. > > I get a few of these nearly every day. I've been assuming they are benign.
this error sets off alarms for me. the comment in the code is "BUG", and naively, i can't work out a) why the author added that comment, b) what superWrite would be competing with for a lock on the superblock (blockWrite returns 0 if it !vtCanLock from _cacheLocalLookup), and c) why superWrite isn't doing a vtLock rather than a vtCanLock, and d) what happens if b is stll dirty (as per comment) and a crash occurs. can someone explain why these are all okay? - erik
