[Gluster-users] GlusterFS 3.6.2: Can't mount GlusterFS volume

[Andreas Hollaus]

The local brick is available, but there's no guarantee that the remote 
brick (the replica) is available at the time glusterd is started. Would 
that put GlusterFS in a bad state which isn't resolved automatically 
when that brick is available again? Would that be the reason why I have 
to start the volume again, even though the command 'gluster volume info' 
claims that it's started?

Regards
Andreas

On 6/22/2015 4:27 PM, Niels de Vos wrote:
> On Mon, Jun 22, 2015 at 03:35:56PM +0200, Andreas Hollaus wrote:
>> Hi,
>>
>> I keep having this situation where I have to start the volume using the force
>> option.Why isn't the volume started without this?
>> It seems to have these problems after a node restart, but I expected the volume to be
>> restarted properly whenever the service is restarted.
> If this only happens "after a node restart", you may want to verify that
> the mountpoints for the bricks are available when glusterd starts the
> brick processes for the volume.
>
> HTH,
> Niels
>
>>
>> Regards
>> Andreas
>>
>> On 06/22/15 10:40, Andreas Hollaus wrote:
>>> Hi,
>>>
>>> Well that did the trick. Thanks!
>>>
>>>
>>> Regards
>>> Andreas
>>>
>>>
>>> On 06/22/15 10:07, Sakshi Bansal wrote:
>>>> Both the bricks are down. Can you run -
>>>> $ gluster volume start <volume-name> force
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users at gluster.org
>>> http://www.gluster.org/mailman/listinfo/gluster-users
>>>
>>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-users