search for: teravolume

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

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>"
...to fix this. I have a feeling it's this "lock" that's not "released" due to the whole setup losing power all of a sudden. I've tried restarting all the nodes, 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/brick...
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>"
...ling it?s > this ?lock? that?s not ?released? due to the whole setup losing power all > of a sudden. I?ve tried restarting all the nodes, 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: gfsn...
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>"
...the whole setup losing power all >> of a sudden. I?ve tried restarting all the nodes, 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: >&gt...
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>"
...lease help if you think you know how to fix this. I have a feeling it?s this ?lock? that?s not ?released? due to the whole setup losing power all of a sudden. I?ve tried restarting all the nodes, 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/brick...
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>"
...ling it?s > this ?lock? that?s not ?released? due to the whole setup losing power all > of a sudden. I?ve tried restarting all the nodes, 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: gfsn...
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>"
...lease help if you think you know how to fix this. I have a feeling it?s this ?lock? that?s not ?released? due to the whole setup losing power all of a sudden. I?ve tried restarting all the nodes, 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/brick...
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>"
...ling it?s > this ?lock? that?s not ?released? due to the whole setup losing power all > of a sudden. I?ve tried restarting all the nodes, 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: gfsn...
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>"
...lease help if you think you know how to fix this. I have a feeling it?s this ?lock? that?s not ?released? due to the whole setup losing power all of a sudden. I?ve tried restarting all the nodes, 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/brick...