[Gluster-users] How to replace a dead brick? (3.6.5)

[Pranith Kumar Karampuri]

On 10/09/2015 01:32 AM, Joe Julian wrote:
>
> On 10/08/2015 11:46 AM, Pranith Kumar Karampuri wrote:
>> On 3.7.4, all you need to do is execute "gluster volume replace-brick 
>> <volname> commit force" and rest will be taken care by afr. We are in 
>> the process of coming up with new commands like "gluster volume 
>> reset-brick <volname> start/commit" for wiping/re-formatting of the 
>> disk. So wait just a little longer :-).
>>
>> Pranith
>>
>
> Nope.
>
>     Volume Name: test
>     Type: Replicate
>     Volume ID: 426a1719-7cc2-4dac-97b4-67491679e00e
>     Status: Started
>     Number of Bricks: 1 x 2 = 2
>     Transport-type: tcp
>     Bricks:
>     Brick1: questor:/tmp/foo1.1
>     Brick2: questor:/tmp/foo1.2
>
>
>     Status of volume: test
>     Gluster process                             TCP Port  RDMA Port
>     Online  Pid
>     ------------------------------------------------------------------------------
>     Brick questor:/tmp/foo1.1                   49162     0 Y       20825
>     Brick questor:/tmp/foo1.2                   49163     0 Y       20859
>     NFS Server on localhost                     N/A       N/A N       N/A
>     Self-heal Daemon on localhost               N/A       N/A Y      
>     20887
>
>
>
> [root at questor]# kill 20825
> [root at questor]# rm -rf /tmp/foo1.1
> [root at questor]# mkdir /tmp/foo1.1
> [root at questor]# gluster volume replace-brick test commit force
> Usage: volume replace-brick <VOLNAME> <SOURCE-BRICK> <NEW-BRICK> 
> {commit force}
> [root at questor]# gluster volume replace-brick test questor:/tmp/foo1.1 
> questor:/tmp/foo1.1 commit force
> volume replace-brick: failed: Brick: questor:/tmp/foo1.1 not 
> available. Brick may be containing or be contained by an existing brick
This is exactly the case that will be covered with "gluster volume 
reset-brick <volname> start/commit"

Pranith
>
>
>> On 10/08/2015 11:26 AM, Lindsay Mathieson wrote:
>>>
>>> On 8 October 2015 at 07:19, Joe Julian <joe at julianfamily.org 
>>> <mailto:joe at julianfamily.org>> wrote:
>>>
>>>     I documented this on my blog at
>>>     https://joejulian.name/blog/replacing-a-brick-on-glusterfs-340/
>>>     which is still accurate for the latest version.
>>>
>>>     The bug report I filed for this was closed without resolution. I
>>>     assume there's no plans for ever making this easy for
>>>     administrators.
>>>     https://bugzilla.redhat.com/show_bug.cgi?id=991084
>>>
>>>
>>>
>>> Yes, its the sort of workaround one can never remember in an 
>>> emergency, you'd have to google it up ...
>>>
>>> In the case I was working with, probably easier and quicker to do a 
>>> remove-brick/add-brick.
>>>
>>> thanks,
>>>
>>>
>>> -- 
>>> Lindsay
>>>
>>>
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users at gluster.org
>>> http://www.gluster.org/mailman/listinfo/gluster-users
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151009/dbe15764/attachment.html>