"Incorrect brick" errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/08/13 18:24, Toby Corkindale wrote:
> Hi,
> I'm getting some confusing "Incorrect brick" errors when attempting to
> remove OR replace a brick.
>
> gluster> volume info condor
>
> Volume Name: condor
> Type: Replicate
> Volume ID: 9fef3f76-525f-4bfe-9755-151e0d8279fd
> Status: Started
> Number of Bricks: 1 x 2 = 2
> Transport-type: tcp
> Bricks:
> Brick1: mel-storage01:/srv/brick/condor
> Brick2: mel-storage02:/srv/brick/condor
>
> gluster> volume remove-brick condor replica 1
> mel-storage02:/srv/brick/condor start
> Incorrect brick mel-storage02:/srv/brick/condor for volume condor
>
>
> If that is the incorrect brick, then what have I done wrong?

Note that the log files don't seem to be any use here, they just report:


E [glusterd-brick-ops.c:749:glusterd_handle_remove_brick] 0-: Incorrect 
brick mel-storage02:/srv/brick/condor for volume condor



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux