search for: gl01

...gt;> >>> then the commands I need to run would be: >>> >>> gluster volume reset-brick export ovirt01.localdomain.local:/gluster/brick3/export >>> start >>> gluster volume reset-brick export ovirt01.localdomain.local:/gluster/brick3/export >>> gl01.localdomain.local:/gluster/brick3/export commit force >>> >>> Correct? >>> >> >> Yes, correct. gl01.localdomain.local should resolve correctly on all 3 >> nodes. >> > > > It fails at first step: > > [root at ovirt01 ~]# gluster volu...

...then the commands I need to run would be: >>>> >>>> gluster volume reset-brick export ovirt01.localdomain.local:/gluster/brick3/export >>>> start >>>> gluster volume reset-brick export ovirt01.localdomain.local:/gluster/brick3/export >>>> gl01.localdomain.local:/gluster/brick3/export commit force >>>> >>>> Correct? >>>> >>> >>> Yes, correct. gl01.localdomain.local should resolve correctly on all 3 >>> nodes. >>> >> >> >> It fails at first step: >...

...need to run would be: >>>>> >>>>> gluster volume reset-brick export ovirt01.localdomain.local:/gluster/brick3/export >>>>> start >>>>> gluster volume reset-brick export ovirt01.localdomain.local:/gluster/brick3/export >>>>> gl01.localdomain.local:/gluster/brick3/export commit force >>>>> >>>>> Correct? >>>>> >>>> >>>> Yes, correct. gl01.localdomain.local should resolve correctly on all 3 >>>> nodes. >>>> >>> >>> &...

...sterd log of that particular node. >>> >>> >> >> Ok, done. >> >> Command executed on ovirt01 with timestamp "2017-07-06 13:04:12" in >> glusterd log files >> >> [root at ovirt01 export]# gluster volume reset-brick export >> gl01.localdomain.local:/gluster/brick3/export start >> volume reset-brick: success: reset-brick start operation successful >> >> [root at ovirt01 export]# gluster volume reset-brick export >> gl01.localdomain.local:/gluster/brick3/export >> ovirt01.localdomain.local:/gluste...

...sterd log of that particular node. >>> >>> >> >> Ok, done. >> >> Command executed on ovirt01 with timestamp "2017-07-06 13:04:12" in >> glusterd log files >> >> [root at ovirt01 export]# gluster volume reset-brick export >> gl01.localdomain.local:/gluster/brick3/export start >> volume reset-brick: success: reset-brick start operation successful >> >> [root at ovirt01 export]# gluster volume reset-brick export >> gl01.localdomain.local:/gluster/brick3/export >> ovirt01.localdomain.local:/gluste...

.... Currently on "export" volume in fact I have this [root at ovirt01 ~]# gluster volume info export Volume Name: export Type: Replicate Volume ID: b00e5839-becb-47e7-844f-6ce6ce1b7153 Status: Started Snapshot Count: 0 Number of Bricks: 0 x (2 + 1) = 1 Transport-type: tcp Bricks: Brick1: gl01.localdomain.local:/gluster/brick3/export Options Reconfigured: ... While on the other two nodes [root at ovirt02 ~]# gluster volume info export Volume Name: export Type: Replicate Volume ID: b00e5839-becb-47e7-844f-6ce6ce1b7153 Status: Started Snapshot Count: 0 Number of Bricks: 0 x (2 + 1) = 2...

...ute the reset-brick command (do I have > to set debug for the the nodes too?) > You have to set the log level to debug for glusterd instance where the commit fails and share the glusterd log of that particular node. > > > [root at ovirt01 ~]# gluster volume reset-brick export > gl01.localdomain.local:/gluster/brick3/export start > volume reset-brick: success: reset-brick start operation successful > > [root at ovirt01 ~]# gluster volume reset-brick export > gl01.localdomain.local:/gluster/brick3/export ovirt01.localdomain.local:/gluster/brick3/export > commit fo...

...e44-8e15-9bff6245d689 state=3 hostname1=ovirt02.localdomain.local hostname2=10.10.2.103 uuid=e9717281-a356-42aa-a579-a4647a29a0bc state=3 hostname1=ovirt01.localdomain.local hostname2=10.10.2.102 [root at ovirt03 ~]# But not the gluster info on the second and third node that have lost the ovirt01/gl01 host brick information... Eg on ovirt02 [root at ovirt02 peers]# gluster volume info export Volume Name: export Type: Replicate Volume ID: b00e5839-becb-47e7-844f-6ce6ce1b7153 Status: Started Snapshot Count: 0 Number of Bricks: 0 x (2 + 1) = 2 Transport-type: tcp Bricks: Brick1: ovirt02.localdo...

...localdomain.local > hostname2=10.10.2.103 > uuid=e9717281-a356-42aa-a579-a4647a29a0bc > state=3 > hostname1=ovirt01.localdomain.local > hostname2=10.10.2.102 > [root at ovirt03 ~]# > > > But not the gluster info on the second and third node that have lost the > ovirt01/gl01 host brick information... > > Eg on ovirt02 > > > [root at ovirt02 peers]# gluster volume info export > > Volume Name: export > Type: Replicate > Volume ID: b00e5839-becb-47e7-844f-6ce6ce1b7153 > Status: Started > Snapshot Count: 0 > Number of Bricks: 0 x (2 + 1)...

On Thu, Jul 6, 2017 at 3:47 AM, Gianluca Cecchi <gianluca.cecchi at gmail.com> wrote: > On Wed, Jul 5, 2017 at 6:39 PM, Atin Mukherjee <amukherj at redhat.com> > wrote: > >> OK, so the log just hints to the following: >> >> [2017-07-05 15:04:07.178204] E [MSGID: 106123] >> [glusterd-mgmt.c:1532:glusterd_mgmt_v3_commit] 0-management: Commit >>

....hp\/._SB 3290: 5f 50 43 49 30 4c 50 43 42 48 5f 45 43 42 31 44 _PCI0LPCBH_ECB1D 32a0: 46 5c 2e 5f 53 42 5f 42 46 43 43 a0 43 06 93 68 F\._SB_BFCC.C..h 32b0: 0a 03 a0 16 90 44 54 53 45 94 54 43 4e 54 01 54 .....DTSE.TCNT.T 32c0: 52 41 50 54 52 54 44 0a 1e 70 7b 47 4c 30 31 01 RAPTRTD..p{GL01. 32d0: 00 47 42 46 30 7b 47 4c 30 31 0a fe 47 4c 30 31 .GBF0{GL01..GL01 32e0: 70 7b 47 4c 30 34 0a 48 00 47 42 46 31 7b 47 4c p{GL04.H.GBF1{GL 32f0: 30 34 0a b7 47 4c 30 34 70 7b 47 4c 30 36 01 00 04..GL04p{GL06.. 3300: 47 42 46 32 7b 47 4c 30 36 0a fe 47 4c 30 36 a0 GBF2{GL06..GL06....