Probably should have checked the logs to see what the problem was. The "force"
command overrides things like preventing adding a brick directory that exists
on your root partition (like when you forget to mount your raid volume).
On March 19, 2014 9:14:41 AM PDT, Jon Tegner <[email protected]> wrote:
>I managed to add the brick by using the "force"-flag, i.e.,
>
>
>"gluster volume add-brick gluster s1:/mnt/raid6 force"
>
>Hopefully there are no drawbacks involved with this...
>
>/jon
>
>On 19/03/14 12:17, [email protected] wrote:
>> Hi,
>>
>> One of my bricks suffered from complete raid failure, (3 disks on
>> raid6). I created a new raid, and wanted to bring the brick back up
>in
>> the volume. Did the following
>> 1. Removed it with
>> gluster volume remove-brick gluster s1:/mnt/raid6 start
>> gluster volume remove-brick gluster s1:/mnt/raid6 commit
>>
>> 2. Detached with
>> gluster peer detach s1
>>
>> 3. Probed anew:
>> gluster peer probe s1
>>
>> 4. Tried to add with
>> gluster volume add-brick gluster s1:/mnt/raid6
>>
>> But last one fails with
>> Stage failed on operation 'Volume Add brick'
>>
>> I'm using 3.4.2.
>>
>> Thanks,
>>
>> /jon
>>
>>
>> _______________________________________________
>> Gluster-users mailing list
>> [email protected]
>> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Gluster-users mailing list
>[email protected]
>http://supercolony.gluster.org/mailman/listinfo/gluster-users
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
