Follow the steps at:
http://gluster.readthedocs.org/en/latest/Administrator%20Guide/Managing%20Volumes/#replace-brick
Read the steps at section:
"Replacing brick in Replicate/Distributed Replicate volumes".
We are working on making all the extra steps vanish and just one command
will take care of everything going forward. Will update gluster-users
once that happens.
Pranith
On 10/09/2015 12:50 AM, Gene Liverman wrote:
So... this kinda applies to me too and I want to get some
clarification: I have the following setup
# gluster volume info
Volume Name: gv0
Type: Replicate
Volume ID: fc50d049-cebe-4a3f-82a6-748847226099
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: eapps-gluster01:/export/sdb1/gv0
Brick2: eapps-gluster02:/export/sdb1/gv0
Brick3: eapps-gluster03:/export/sdb1/gv0
Options Reconfigured:
diagnostics.count-fop-hits: on
diagnostics.latency-measurement: on
nfs.drc: off
eapps-gluster03 had a hard drive failure so I replaced it, formatted
the drive and now need gluster to be happy again. Gluster put a
.glusterfs folder in /export/sdb1/gv0 but nothing else has shown up
and the brick is offline. I read the docs on replacing a brick but
seem to be missing something and would appreciate some help. Thanks!
--
*Gene Liverman*
Systems Integration Architect
Information Technology Services
University of West Georgia
[email protected] <mailto:[email protected]>
ITS: Making Technology Work for You!
On Thu, Oct 8, 2015 at 2:46 PM, Pranith Kumar Karampuri
<[email protected] <mailto:[email protected]>> 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
On 10/08/2015 11:26 AM, Lindsay Mathieson wrote:
On 8 October 2015 at 07:19, Joe Julian <[email protected]
<mailto:[email protected]>> 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
[email protected] <mailto:[email protected]>
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected] <mailto:[email protected]>
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
