<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">On 23/05/19 2:40 AM, Alan Orth wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKKdN4VP6ome2h2_iXaRVdr+WNp7K6PssCBpOffOn547P9R3Dw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Dear list,
<div><br>
</div>
<div>I seem to have gotten into a tricky situation. Today I
brought up a shiny new server with new disk arrays and
attempted to replace one brick of a replica 2
distribute/replicate volume on an older server using the
`replace-brick` command:</div>
<div><br>
</div>
<div># gluster volume replace-brick homes
wingu0:/mnt/gluster/homes wingu06:/data/glusterfs/sdb/homes
commit force</div>
<div><br>
</div>
<div>The command was successful and I see the new brick in the
output of `gluster volume info`. The problem is that Gluster
doesn't seem to be migrating the data, </div>
</div>
</blockquote>
<p>`replace-brick` definitely must heal (not migrate) the data. In
your case, data must have been healed from Brick-4 to the replaced
Brick-3. Are there any errors in the self-heal daemon logs of
Brick-4's node? Does Brick-4 have pending AFR xattrs blaming
Brick-3? The doc is a bit out of date. replace-brick command
internally does all the setfattr steps that are mentioned in the
doc.</p>
<p>-Ravi<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAKKdN4VP6ome2h2_iXaRVdr+WNp7K6PssCBpOffOn547P9R3Dw@mail.gmail.com">
<div dir="ltr">
<div>and now the original brick that I replaced is no longer
part of the volume (and a few terabytes of data are just
sitting on the old brick):</div>
<div><br>
</div>
<div># gluster volume info homes | grep -E "Brick[0-9]:"<br>
Brick1: wingu4:/mnt/gluster/homes<br>
Brick2: wingu3:/mnt/gluster/homes<br>
Brick3: wingu06:/data/glusterfs/sdb/homes<br>
Brick4: wingu05:/data/glusterfs/sdb/homes<br>
Brick5: wingu05:/data/glusterfs/sdc/homes<br>
Brick6: wingu06:/data/glusterfs/sdc/homes</div>
<br>
<div>I see the Gluster docs have a more complicated procedure
for replacing bricks that involves getfattr/setfattr¹. How can
I tell Gluster about the old brick? I see that I have a backup
of the old volfile thanks to yum's rpmsave function if that
helps.<br>
</div>
<div><br>
</div>
<div>We are using Gluster 5.6 on CentOS 7. Thank you for any
advice you can give.<br>
</div>
<div><br>
</div>
<div>¹ <a
href="https://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/#replace-faulty-brick"
moz-do-not-send="true">https://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/#replace-faulty-brick</a></div>
<div><br>
</div>
<div>-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Alan Orth<br>
<a href="mailto:alan.orth@gmail.com" target="_blank"
moz-do-not-send="true">alan.orth@gmail.com</a><br>
<a href="https://picturingjordan.com" target="_blank"
moz-do-not-send="true">https://picturingjordan.com</a><br>
<a href="https://englishbulgaria.net" target="_blank"
moz-do-not-send="true">https://englishbulgaria.net</a><br>
<a href="https://mjanja.ch" target="_blank"
moz-do-not-send="true">https://mjanja.ch</a><br>
"In heaven all the interesting people are missing."
―Friedrich Nietzsche</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
</body>
</html>