search for: gfsnode1

Displaying 8 results from an estimated 8 matches for "gfsnode1".

Did you mean: gfsnode3
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 21
2
Gluster failure due to "0-management: Lock not released for <volumename>"
...restarting glusterfs-server etc. I'm out of ideas. Thanks in advance! Victor Volume Name: teravolume Type: Distributed-Replicate Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 Status: Started Snapshot Count: 0 Number of Bricks: 3 x 2 = 6 Transport-type: tcp Bricks: Brick1: gfsnode1:/media/brick1 Brick2: gfsnode2:/media/brick1 Brick3: gfsnode3:/media/brick1 Brick4: gfsnode1:/media/brick2 Brick5: gfsnode2:/media/brick2 Brick6: gfsnode3:/media/brick2 Options Reconfigured: nfs.disable: on [2017-06-21 16:02:52.376709] W [MSGID: 106118] [glusterd-handler.c:5913:__glus...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 22
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...r > > > > Volume Name: teravolume > > Type: Distributed-Replicate > > Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 > > Status: Started > > Snapshot Count: 0 > > Number of Bricks: 3 x 2 = 6 > > Transport-type: tcp > > Bricks: > > Brick1: gfsnode1:/media/brick1 > > Brick2: gfsnode2:/media/brick1 > > Brick3: gfsnode3:/media/brick1 > > Brick4: gfsnode1:/media/brick2 > > Brick5: gfsnode2:/media/brick2 > > Brick6: gfsnode3:/media/brick2 > > Options Reconfigured: > > nfs.disable: on > > > > &g...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 27
2
Gluster failure due to "0-management: Lock not released for <volumename>"
...Type: Distributed-Replicate >> >> Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 >> >> Status: Started >> >> Snapshot Count: 0 >> >> Number of Bricks: 3 x 2 = 6 >> >> Transport-type: tcp >> >> Bricks: >> >> Brick1: gfsnode1:/media/brick1 >> >> Brick2: gfsnode2:/media/brick1 >> >> Brick3: gfsnode3:/media/brick1 >> >> Brick4: gfsnode1:/media/brick2 >> >> Brick5: gfsnode2:/media/brick2 >> >> Brick6: gfsnode3:/media/brick2 >> >> Options Reconfigured:...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 29
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...des, restarting glusterfs-server etc. I?m out of ideas. Thanks in advance! Victor Volume Name: teravolume Type: Distributed-Replicate Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 Status: Started Snapshot Count: 0 Number of Bricks: 3 x 2 = 6 Transport-type: tcp Bricks: Brick1: gfsnode1:/media/brick1 Brick2: gfsnode2:/media/brick1 Brick3: gfsnode3:/media/brick1 Brick4: gfsnode1:/media/brick2 Brick5: gfsnode2:/media/brick2 Brick6: gfsnode3:/media/brick2 Options Reconfigured: nfs.disable: on [2017-06-21 16:02:52.376709] W [MSGID: 106118] [glusterd-handler.c:5913:__glus...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 30
3
Gluster failure due to "0-management: Lock not released for <volumename>"
...r > > > > Volume Name: teravolume > > Type: Distributed-Replicate > > Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 > > Status: Started > > Snapshot Count: 0 > > Number of Bricks: 3 x 2 = 6 > > Transport-type: tcp > > Bricks: > > Brick1: gfsnode1:/media/brick1 > > Brick2: gfsnode2:/media/brick1 > > Brick3: gfsnode3:/media/brick1 > > Brick4: gfsnode1:/media/brick2 > > Brick5: gfsnode2:/media/brick2 > > Brick6: gfsnode3:/media/brick2 > > Options Reconfigured: > > nfs.disable: on > > > > &g...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jul 04
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...des, restarting glusterfs-server etc. I?m out of ideas. Thanks in advance! Victor Volume Name: teravolume Type: Distributed-Replicate Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 Status: Started Snapshot Count: 0 Number of Bricks: 3 x 2 = 6 Transport-type: tcp Bricks: Brick1: gfsnode1:/media/brick1 Brick2: gfsnode2:/media/brick1 Brick3: gfsnode3:/media/brick1 Brick4: gfsnode1:/media/brick2 Brick5: gfsnode2:/media/brick2 Brick6: gfsnode3:/media/brick2 Options Reconfigured: nfs.disable: on [2017-06-21 16:02:52.376709] W [MSGID: 106118] [glusterd-handler.c:5913:__glus...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jul 05
1
Gluster failure due to "0-management: Lock not released for <volumename>"
...r > > > > Volume Name: teravolume > > Type: Distributed-Replicate > > Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 > > Status: Started > > Snapshot Count: 0 > > Number of Bricks: 3 x 2 = 6 > > Transport-type: tcp > > Bricks: > > Brick1: gfsnode1:/media/brick1 > > Brick2: gfsnode2:/media/brick1 > > Brick3: gfsnode3:/media/brick1 > > Brick4: gfsnode1:/media/brick2 > > Brick5: gfsnode2:/media/brick2 > > Brick6: gfsnode3:/media/brick2 > > Options Reconfigured: > > nfs.disable: on > > > > &g...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jul 04
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...des, restarting glusterfs-server etc. I?m out of ideas. Thanks in advance! Victor Volume Name: teravolume Type: Distributed-Replicate Volume ID: 85af74d0-f1bc-4b0d-8901-4dea6e4efae5 Status: Started Snapshot Count: 0 Number of Bricks: 3 x 2 = 6 Transport-type: tcp Bricks: Brick1: gfsnode1:/media/brick1 Brick2: gfsnode2:/media/brick1 Brick3: gfsnode3:/media/brick1 Brick4: gfsnode1:/media/brick2 Brick5: gfsnode2:/media/brick2 Brick6: gfsnode3:/media/brick2 Options Reconfigured: nfs.disable: on [2017-06-21 16:02:52.376709] W [MSGID: 106118] [glusterd-handler.c:5913:__glus...