Gluster users - Aug 2016 - Distribute only volume access during failure

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?
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.

Thanks.

Regards,
Lionel BEARD

________________________________

Ce message et toutes les pi?ces jointes (ci-apr?s le "message") sont
?tablis ? l'intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur ou s'il ne vous est pas destin?, merci
de le d?truire ainsi que toute copie de votre syst?me et d'en avertir
imm?diatement l'exp?diteur. Toute lecture non autoris?e, toute utilisation
de ce message qui n'est pas conforme ? sa destination, toute diffusion ou
toute publication, totale ou partielle, est interdite. L'Internet ne
permettant pas d'assurer l'int?grit? de ce message ?lectronique
susceptible d'alt?ration, l'exp?diteur (et ses filiales) d?cline(nt)
toute responsabilit? au titre de ce message dans l'hypoth?se o? il aurait
?t? modifi? ou falsifi?.

This message and any attachments (the "message") is intended solely
for the intended recipient(s) and is confidential. If you receive this message
in error, or are not the intended recipient(s), please delete it and any copies
from your systems and immediately notify the sender. Any unauthorized view, use
that does not comply with its purpose, dissemination or disclosure, either whole
or partial, is prohibited. Since the internet cannot guarantee the integrity of
this message which may not be reliable, the sender (and its subsidiaries) shall
not be liable for the message if modified or falsified.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160823/dc9e96f4/attachment.html>

Hi,

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)
OR
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.

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