Displaying 12 results from an estimated 12 matches for "ws_brick".
2017 Jul 07
0
[Gluster-devel] gfid and volume-id extended attributes lost
...glusterfs2 and glusterfs3 again.
[root at glusterfs2 Log_Files]# gluster volume info
Volume Name: StoragePool
Type: Distributed-Disperse
Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
Status: Started
Number of Bricks: 20 x (2 + 1) = 60
Transport-type: tcp
Bricks:
Brick1: glusterfs1sds:/ws/disk1/ws_brick
Brick2: glusterfs2sds:/ws/disk1/ws_brick
Brick3: glusterfs3sds:/ws/disk1/ws_brick
Brick4: glusterfs1sds:/ws/disk2/ws_brick
Brick5: glusterfs2sds:/ws/disk2/ws_brick
Brick6: glusterfs3sds:/ws/disk2/ws_brick
Brick7: glusterfs1sds:/ws/disk3/ws_brick
Brick8: glusterfs2sds:/ws/disk3/ws_brick
Brick9: glus...
2017 Jul 08
2
[Gluster-devel] gfid and volume-id extended attributes lost
...t;
>
>
> Volume Name: StoragePool
>
> Type: Distributed-Disperse
>
> Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
>
> Status: Started
>
> Number of Bricks: 20 x (2 + 1) = 60
>
> Transport-type: tcp
>
> Bricks:
>
> Brick1: glusterfs1sds:/ws/disk1/ws_brick
>
> Brick2: glusterfs2sds:/ws/disk1/ws_brick
>
> Brick3: glusterfs3sds:/ws/disk1/ws_brick
>
> Brick4: glusterfs1sds:/ws/disk2/ws_brick
>
> Brick5: glusterfs2sds:/ws/disk2/ws_brick
>
> Brick6: glusterfs3sds:/ws/disk2/ws_brick
>
> Brick7: glusterfs1sds:/ws/disk3/ws...
2017 Jul 07
3
[Gluster-devel] gfid and volume-id extended attributes lost
On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com>
wrote:
> 3.7.19
>
These are the only callers for removexattr and only _posix_remove_xattr has
the potential to do removexattr as posix_removexattr already makes sure
that it is not gfid/volume-id. And surprise surprise _posix_remove_xattr
happens only from healing code of afr/ec. And this can only happen
2017 Jul 10
0
[Gluster-devel] gfid and volume-id extended attributes lost
...> Type: Distributed-Disperse
>>
>> Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
>>
>> Status: Started
>>
>> Number of Bricks: 20 x (2 + 1) = 60
>>
>> Transport-type: tcp
>>
>> Bricks:
>>
>> Brick1: glusterfs1sds:/ws/disk1/ws_brick
>>
>> Brick2: glusterfs2sds:/ws/disk1/ws_brick
>>
>> Brick3: glusterfs3sds:/ws/disk1/ws_brick
>>
>> Brick4: glusterfs1sds:/ws/disk2/ws_brick
>>
>> Brick5: glusterfs2sds:/ws/disk2/ws_brick
>>
>> Brick6: glusterfs3sds:/ws/disk2/ws_brick
>...
2017 Jul 10
2
[Gluster-devel] gfid and volume-id extended attributes lost
...;>> Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
>>>
>>> Status: Started
>>>
>>> Number of Bricks: 20 x (2 + 1) = 60
>>>
>>> Transport-type: tcp
>>>
>>> Bricks:
>>>
>>> Brick1: glusterfs1sds:/ws/disk1/ws_brick
>>>
>>> Brick2: glusterfs2sds:/ws/disk1/ws_brick
>>>
>>> Brick3: glusterfs3sds:/ws/disk1/ws_brick
>>>
>>> Brick4: glusterfs1sds:/ws/disk2/ws_brick
>>>
>>> Brick5: glusterfs2sds:/ws/disk2/ws_brick
>>>
>>> Brick...
2017 Jul 10
0
[Gluster-devel] gfid and volume-id extended attributes lost
...bf0f-f5691208531f
>>>>
>>>> Status: Started
>>>>
>>>> Number of Bricks: 20 x (2 + 1) = 60
>>>>
>>>> Transport-type: tcp
>>>>
>>>> Bricks:
>>>>
>>>> Brick1: glusterfs1sds:/ws/disk1/ws_brick
>>>>
>>>> Brick2: glusterfs2sds:/ws/disk1/ws_brick
>>>>
>>>> Brick3: glusterfs3sds:/ws/disk1/ws_brick
>>>>
>>>> Brick4: glusterfs1sds:/ws/disk2/ws_brick
>>>>
>>>> Brick5: glusterfs2sds:/ws/disk2/ws_brick...
2017 Jul 10
2
[Gluster-devel] gfid and volume-id extended attributes lost
...glusterfs2 and glusterfs3 again.
[root at glusterfs2 Log_Files]# gluster volume info
Volume Name: StoragePool
Type: Distributed-Disperse
Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
Status: Started
Number of Bricks: 20 x (2 + 1) = 60
Transport-type: tcp
Bricks:
Brick1: glusterfs1sds:/ws/disk1/ws_brick
Brick2: glusterfs2sds:/ws/disk1/ws_brick
Brick3: glusterfs3sds:/ws/disk1/ws_brick
Brick4: glusterfs1sds:/ws/disk2/ws_brick
Brick5: glusterfs2sds:/ws/disk2/ws_brick
Brick6: glusterfs3sds:/ws/disk2/ws_brick
Brick7: glusterfs1sds:/ws/disk3/ws_brick
Brick8: glusterfs2sds:/ws/disk3/ws_brick
Brick9: glus...
2017 Jul 13
0
[Gluster-devel] gfid and volume-id extended attributes lost
...t;
>
>
> Volume Name: StoragePool
>
> Type: Distributed-Disperse
>
> Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f
>
> Status: Started
>
> Number of Bricks: 20 x (2 + 1) = 60
>
> Transport-type: tcp
>
> Bricks:
>
> Brick1: glusterfs1sds:/ws/disk1/ws_brick
>
> Brick2: glusterfs2sds:/ws/disk1/ws_brick
>
> Brick3: glusterfs3sds:/ws/disk1/ws_brick
>
> Brick4: glusterfs1sds:/ws/disk2/ws_brick
>
> Brick5: glusterfs2sds:/ws/disk2/ws_brick
>
> Brick6: glusterfs3sds:/ws/disk2/ws_brick
>
> Brick7: glusterfs1sds:/ws/disk3/ws...
2018 Jan 09
2
Bricks to sub-volume mapping
...h sub-volumes in case of disperse volume, for example in below volume has two sub-volumes :
Type: Distributed-Disperse
Volume ID: 6dc8ced8-27aa-4481-bfe8-057133c31d0b
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x (4 + 2) = 12
Transport-type: tcp
Bricks:
Brick1: pdchyperscale1sds:/ws/disk1/ws_brick
Brick2: pdchyperscale2sds:/ws/disk1/ws_brick
Brick3: pdchyperscale3sds:/ws/disk1/ws_brick
Brick4: pdchyperscale1sds:/ws/disk2/ws_brick
Brick5: pdchyperscale2sds:/ws/disk2/ws_brick
Brick6: pdchyperscale3sds:/ws/disk2/ws_brick
Brick7: pdchyperscale1sds:/ws/disk3/ws_brick
Brick8: pdchyperscale2sds:/ws...
2018 Jan 09
0
Bricks to sub-volume mapping
...b-volumes :
>
> Type: Distributed-Disperse
>
> Volume ID: 6dc8ced8-27aa-4481-bfe8-057133c31d0b
>
> Status: Started
>
> Snapshot Count: 0
>
> Number of Bricks: 2 x (4 + 2) = 12
>
> Transport-type: tcp
>
> Bricks:
>
> Brick1: pdchyperscale1sds:/ws/disk1/ws_brick
>
> Brick2: pdchyperscale2sds:/ws/disk1/ws_brick
>
> Brick3: pdchyperscale3sds:/ws/disk1/ws_brick
>
> Brick4: pdchyperscale1sds:/ws/disk2/ws_brick
>
> Brick5: pdchyperscale2sds:/ws/disk2/ws_brick
>
> Brick6: pdchyperscale3sds:/ws/disk2/ws_brick
>
> Brick7: pdchyp...
2018 Jan 09
2
Bricks to sub-volume mapping
...h sub-volumes in case of disperse volume, for example in below volume has two sub-volumes :
Type: Distributed-Disperse
Volume ID: 6dc8ced8-27aa-4481-bfe8-057133c31d0b
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x (4 + 2) = 12
Transport-type: tcp
Bricks:
Brick1: pdchyperscale1sds:/ws/disk1/ws_brick
Brick2: pdchyperscale2sds:/ws/disk1/ws_brick
Brick3: pdchyperscale3sds:/ws/disk1/ws_brick
Brick4: pdchyperscale1sds:/ws/disk2/ws_brick
Brick5: pdchyperscale2sds:/ws/disk2/ws_brick
Brick6: pdchyperscale3sds:/ws/disk2/ws_brick
Brick7: pdchyperscale1sds:/ws/disk3/ws_brick
Brick8: pdchyperscale2sds:/ws...
2018 Jan 09
0
Bricks to sub-volume mapping
...Distributed-Disperse
>
> Volume ID: 6dc8ced8-27aa-4481-bfe8-057133c31d0b
>
> Status: Started
>
> Snapshot Count: 0
>
> Number of Bricks: 2 x (4 + 2) = 12
>
> Transport-type: tcp
>
> Bricks:
>
> Brick1: pdchyperscale1sds:/ws/disk1/ws_brick
>
> Brick2: pdchyperscale2sds:/ws/disk1/ws_brick
>
> Brick3: pdchyperscale3sds:/ws/disk1/ws_brick
>
> Brick4: pdchyperscale1sds:/ws/disk2/ws_brick
>
> Brick5: pdchyperscale2sds:/ws/disk2/ws_brick
>
> Brick6: pdchyperscale3sds:/ws/disk2/ws_brick
>...