[Gluster-users] Distribute only volume access during failure

Saravanakumar Arumugam sarumuga at redhat.com
Tue Aug 23 11:38:53 UTC 2016


On 08/23/2016 03:09 PM, Beard Lionel (BOSTON-STORAGE) wrote:
> Hi,
> I have noticed that when using a distribute volume, if a brick is not 
> accessible, volume is still accessible in read-write mode, but some 
> files can’t be created (depending on filename).
> Is it possible to force a distribute volume to be put in read-only 
> mode during a brick failure, to avoid random access error?
You can either remount the volume as read-only.  ( mount with "ro" option)
You can set the volume read-only. (gluster volume set <volume name> 
read-only on)

> I’m afraid of application behavior in this case, when only some files 
> are not accessible. I prefer to have volume not writeable when a brick 
> failed.
It is better to configure a distribute replicate volume, so that volume 
is accessible(and writable) even if one node is down.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160823/5de117ca/attachment.html>

More information about the Gluster-users mailing list