>
> If set this option to "none", writting on S1 is OK while S2 if rebooting
> but writting to S2 while S1 is rebooting is not possible.
Edit : stoping the current writting on S2 and restarting it works...
I don't need to do that on S1...
--
Cordialement / Best regar
ype
>
> Thanks
> JF
>
Thank,
If set this option to "none", writting on S1 is OK while S2 if rebooting
but writting to S2 while S1 is rebooting is not possible.
--
Cordialement / Best regards, Michaël Couren,
ABES, Montpellier, France.
_
/ Best regards, Michaël Couren,
ABES, Montpellier, France.
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
l.
Global performances are mainly those of the machines homing glusterfs
(VMs on SAN perf are 50% those of baremetal local disk)
--
Cordialement / Best regards, Michaël Couren,
ABES, Montpellier, France.
___
Gluster-users mailing list
Gluster-users@gluster
766:client3_3_lookup_cbk]
0-gv0-client-0: remote operation failed: No such file or directory. Path:
(b3ad11a0-2027-4712--snip)
Than I had to stop the other brick because we are on production. Logs do not
grow since...
--
Cordialement / Best regards, Michaël Couren,
A
a way to reduce verbosity ?
Thanks
--
Cordialement / Best regards, Michaël Couren,
ABES, Montpellier, France.
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users