search for: datastore_temp

Displaying 4 results from an estimated 4 matches for "datastore_temp".

2018 Feb 23
1
Problem migration 3.7.6 to 3.13.2
Thanks for replay. I founded this values datastore_temp.serda1.glusterfs-p1-b1.vol: option shared-brick-count 2 datastore_temp.serda1.glusterfs-p2-b2.vol: option shared-brick-count 2 datastore_temp.serda2.glusterfs-p1-b1.vol: option shared-brick-count 0 datastore_temp.serda2.glusterfs-p2-b2.vol: option shared-brick-count 0 I need to change...
2018 Feb 23
0
Problem migration 3.7.6 to 3.13.2
Hi Daniele, Do you mean that the df -h output is incorrect for the volume post the upgrade? If yes and the bricks are on separate partitions, you might be running into [1]. Can you search for the string "option shared-brick-count" in the files in /var/lib/glusterd/vols/<volumename> and let us know the value? The workaround to get this working on the cluster is available in [2].
2018 Feb 24
0
Failed heal volume
...sabling sockopt IPV6_V6ONLY: "Protocollo non disponibile" [2018-02-24 15:32:00.915854] I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2018-02-24 15:32:01.925714] E [MSGID: 114058] [client-handshake.c:1571:client_query_portmap_cbk] 0-datastore_temp-client-1: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running. [2018-02-24 15:32:01.926632] E [MSGID: 114058] [client-handshake.c:1571:client_query_portmap_cbk] 0-datastore_temp-client-2: failed to get the port...
2018 Feb 23
2
Problem migration 3.7.6 to 3.13.2
I have done a migration to new version of gluster but when i doing a command df -h the result of space are minor of total. Configuration: 2 peers Brick serda2:/glusterfs/p2/b2 49152 0 Y 1560 Brick serda1:/glusterfs/p2/b2 49152 0 Y 1462 Brick serda1:/glusterfs/p1/b1 49153 0 Y 1476 Brick serda2:/glusterfs/p1/b1