:
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
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.
Thanks everybody for the support.
Ivano
On 6/13/14 2:31 PM, Ivano Talamo wrote:
On 6/13/14 1:08 PM, Niels de Vos wrote:
On
, "Ivano Talamo" wrote:
I had done it only on one of the two :(
But even after I've done it on the other server and I've restarted the
gluster daemon I see no change
Ivano
On 6/12/14 8:18 PM, Jae Park wrote:
Have you done the server part too? I mean adding "option
rpc-auth-a
On 6/13/14 1:08 PM, Niels de Vos wrote:
On Fri, Jun 13, 2014 at 09:56:46AM +0200, Ivano Talamo wrote:
I had done it only on one of the two :(
But even after I've done it on the other server and I've restarted
the gluster daemon I see no change
Can you confirm that the issue is still
On 6/13/14 11:56 AM, Vijay Bellur wrote:
I see this in vol1.log and glusterhd.log files:
[2014-06-13 09:44:11.247944] I [rpc-clnt.c:1685:rpc_clnt_reconfig]
0-vol1-client-0: changing port to 49152 (from 0)
[2014-06-13 09:44:11.252518] E [socket.c:2161:socket_connect_finish]
0-vol1-client-0: conn
On 6/12/14 7:58 PM, Vijay Bellur wrote:
Btw, I have problems starting the VM. the "virsh start "
command remains waiting forever on a futex call.
The xml relevant section is:
name='vol1/vms/disks/cmsrm-ui01.qcow2'>
Do you happen t
Jae
On 6/12/14 7:05 AM, "Ivano Talamo" wrote:
On 6/12/14 2:21 PM, Niels de Vos wrote:
On Thu, Jun 12, 2014 at 10:59:23AM +0200, Ivano Talamo wrote:
Hi Jae,
Have you taken care of setting the required glusterd and volume options?
these are described here:
-
http://www.gluster.org/com
On 6/12/14 3:44 PM, Vijay Bellur wrote:
On 06/11/2014 11:25 PM, Ivano Talamo wrote:
Hello,
I recently update 2 servers (Scientific Linux 6) with a replicate volume
from gluster 3.4 to 3.5.0-2.
The volume was previously used to host qemu/kvm VM images accessed via a
fuse-mounted mount-point.
Now
On 6/12/14 2:21 PM, Niels de Vos wrote:
On Thu, Jun 12, 2014 at 10:59:23AM +0200, Ivano Talamo wrote:
Hi Jae,
Have you taken care of setting the required glusterd and volume options?
these are described here:
-
http://www.gluster.org/community/documentation/index.php
, which I
can ignore now.
Beta2 download:
http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.5.1beta2/
Jae
On 6/11/14 10:55 AM, "Ivano Talamo" wrote:
Hello,
I recently update 2 servers (Scientific Linux 6) with a replicate volume
>from gluster 3.4 to 3.5.0-2.
T
Hello,
I recently update 2 servers (Scientific Linux 6) with a replicate volume
from gluster 3.4 to 3.5.0-2.
The volume was previously used to host qemu/kvm VM images accessed via a
fuse-mounted mount-point.
Now I would like to use the libgfapi but I'm seeing this error:
[root@cmsrm-service02
ry
to decrease, but to this rate it would take two weeks to finish, maybe I
would rather delete and recreate the volume
from scratch and with 3.5.
Thanks
Ivano
On 5/27/14 7:35 PM, Ravishankar N wrote:
On 05/27/2014 08:47 PM, Ivano Talamo wrote:
Dear all,
we have a replicated volume (2 servers
Dear all,
we have a replicated volume (2 servers with 1 brick each) on Scientific
Linux 6.2 with gluster 3.4.
Everything was running fine until we shutdown of of the two and kept it
down for 2 months.
When it came up again the volume could be healed and we have the
following symptoms
(call #1
13 matches
Mail list logo
