On Aug 27, 2009, at 5:14 AM, Paul Davis wrote:
I'd be quite surprised to find that it was a 0.9.1 bug that introduced
errors in the code_server process at 4PM PST. I doubt that sort of bug
would go unnoticed for this long :) Granted it could just be masking
the real cause, so who's to say?
Your biggest fear for data loss would be when clients can't connect to
the server because its borked. Once the data gets into couch assuming
you're ensuring a full commit then it should be peachy keen. But I
make no promises. This is the first time I've ever seen error messages
like those so for all I know you could have magic gnomes living in the
server rack.
Yes, this is crazy.
Another change I did along with upgrade is,
changed config "view_index_dir" to other vol not same vol and
directory as "database_dir"
If that activated magic gnomes ? :)
