Comment 1 for bug 485976

Ok, so *something* made zeoraid2 think that zeo1 is failed.

This causes zeoraid2 to stop writing to zeo1. If a transaction goes through zeoraid1 and ends up in both zeo1 and zeo2 then zeo1 will quickly appear as inconsistent which is correct.

I think the major problem here is that you can't see why zeoraid2 is degrading zeo1 which is an issue already described in another bug.