Hi,I would be glad to do it but the problem is that the VM running on the gluster volume are production servers. If you think that we don't risk to lose the VM images and we can rollback to 3.5 in case of problems, I would test it.
Cheers, Ivano On 6/14/14 6:49 PM, Justin Clift wrote:
On 14/06/2014, at 8:06 AM, Ivano Talamo wrote:Hi, even after stopping/starting the volume no change. But that problem seem the #1103413 bug. Using the workaround suggested by Jae Park fixed it and now is working.Out of curiosity, would you have time to test 3.5.1 beta2? The bug you're mentioning is fixed in it, along with a few other bugs as well. And we need testers. ;) Regards and best wishes, Justin CliftThanks everybody for the support. Ivano-- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
