vol repair fails: "no servers available for the mirrors"

[jonesy]

I got a message saying a volume check was done, and 6 degraded volumes were found. I tried to run vol repair n=4, but I get an error:

------------------- snip -----------------------
Starting repair of volume 'AddThis:db_vol'
Failed to repair volume AddThis.user.db_vol - no server available for the mirrors.
Failed to start repairing volume 'AddThis:db_vol'.
--------------------/snip ----------------------

This is a little scary, because the application had been running without issues for a couple of days before this popped up, no content has even been added yet (so none of the volumes have been touched by me), and why did the system let me create volumes that cannot be mirrored?

Thanks for any tips.

[jonesy]

Not that this would be considered a "solution", but I blew away the volume and recreated it (we're not yet in production). Still would like to know what causes the error.

[PeterNic]

Jonesy,

Normally this happens if a server is down and there is no disk space on the remaining servers to allocate a mirror of the volume. From your "recovery" this doesn't appear to be the case.

Please contact our support on this if you haven't already. We will need more details on your grid's configuration and the events leading to the message above. PM me if problems.

Also, in the future, if you want to keep the volume for our support to examine but continue your work, you may simply rename it. Another "recovery" step would be to copy the volume -- this works in most cases when you have enough disk space -- the new copy is mirrored.

Regards,
-- Peter