<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 10pt; color: #000000'><font size="3">Thanks for the pointer.<br><br>Step 1 fails to return a UUID. If I 'gluster peer status' on the working server, I get:<br><br><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Number of Peers: 1</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Hostname: quad</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">Uuid: 03eaca98-ac4f-4b61-9b30-7e1b40b01d9b</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">State: Peer in Cluster (Connected)</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><br>I then go to step 2 with the shown UUID.<br><br>I start glusterd on the failed server and peer probe the working server:<br><br><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">root@quad:~# /etc/init.d/glusterd start</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;"> * Starting glusterd service glusterd [ OK ] </span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">root@quad:~# gluster peer probe thinkpad</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">thinkpad is already part of another cluster</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">root@quad:~# gluster peer status</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">No peers present</span><br style="font-family: courier new,courier,monaco,monospace,sans-serif;"><span style="font-family: courier new,courier,monaco,monospace,sans-serif;">root@quad:~# <br><br>Stuck again.<br><br>Gerald<br><br></span><br></font><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">
<br><font face="sans-serif" size="2">Hi Gerald,</font>
<br>
<br><font face="sans-serif" size="2">The volume and peer information is by
default stored in /etc/glusterd</font>
<br><font face="sans-serif" size="2">which I guess was wiped when you reinstalled.</font>
<br>
<br><font face="sans-serif" size="2">This should help restore the correct
settings</font>
<br><a href="http://europe.gluster.org/community/documentation/index.php/Gluster_3.2:_Brick_Restoration_-_Replace_Crashed_Server" target="_blank"><font color="blue" size="3"><u>http://europe.gluster.org/community/documentation/index.php/Gluster_3.2:_Brick_Restoration_-_Replace_Crashed_Server</u></font></a><font size="3">
</font>
<br>
<br><font face="sans-serif" size="2">Alternatively I believe you can delete
some files in /etc/glusterd</font>
<br><font face="sans-serif" size="2">if you don't want to restore the volume.</font>
<br><font face="sans-serif" size="2">Just not sure which ones :)</font>
<br><font face="sans-serif" size="2"><br>
Best regards,<br>
<br>
Gabriel</font>
<br>
<br><font size="2"><tt>gluster-users-bounces@gluster.org wrote on 05/01/2012
15:10:33:<br>
<br>
> Hi,<br>
> <br>
> I can't stop or delete a replica volume:<br>
> <br>
> # gluster volume info<br>
> <br>
> Volume Name: sync1<br>
> Type: Replicate<br>
> Status: Started<br>
> Number of Bricks: 2<br>
> Transport-type: tcp<br>
> Bricks:<br>
> Brick1: thinkpad:/gluster/export<br>
> Brick2: quad:/raid/gluster/export<br>
> <br>
> # gluster volume stop sync1<br>
> Stopping volume will make its data inaccessible. Do you want to <br>
> continue? (y/n) y<br>
> Volume sync1 does not exist<br>
> <br>
> # gluster volume delete sync1<br>
> Deleting volume will erase all information about the volume. Do you
<br>
> want to continue? (y/n) y<br>
> Volume sync1 has been started.Volume needs to be stopped before deletion.<br>
> <br>
> <br>
> Any ideas? I had to re-install the peers OS, and now the peer
has <br>
> no knowledge of the other system (or the volume).<br>
> <br>
> Gerald<br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> Gluster-users@gluster.org<br>
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users<br>
</tt></font></blockquote><br></div></body></html>