On 8 October 2015 at 07:19, Joe Julian <joe@xxxxxxxxxxxxxxxx> wrote:
thanks,
On 10/07/2015 12:06 AM, Lindsay Mathieson wrote:
First up - one of the things that concerns me re gluster is the incoherent state of documentation. The only docs linked on the main webpage are for 3.2 and there is almost nothing on how to handle failure modes such as dead disks/bricks etc, which is one of glusters primary functions.
Every link under Documentation at http://gluster.org points to the gluster.readthedocs.org pages that are all current. Where is this "main webpage" in which you found links to the old wiki pages?
Which is what came up at the top when i searched for gluster documentation. Might be an idea to redirect to the main docs from that page.
A bit disturbing, I was hoping it would work off the remaining brick.Can't start the datastore1:As a test, I destroyed one brick (zfs destroy the dataset).My problem - I have a replica 2 volume, 2 nodes, 2 bricks (zfs datasets).
volume start: datastore1: failed: Failed to find brick directory /glusterdata/datastore1 for volume datastore1. Reason : No such file or directory
It is still working off the remaining brick. It won't start the missing brick because the missing brick is missing. This is by design. If, for whatever reason, your brick did not mount, you don't want gluster to start filling your root device with replication from the other brick.
It wouldn't start the *Datastore*, so all bricks were unavailable. I did stop the datastore myself in the first place, but I would have expected I could restart it.
--
Lindsay
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
