<html><head></head><body>Notice it actually tells you to look in the logs on server-ip-2 but you did not include any logs from that server.<br><br><div class="gmail_quote">On June 21, 2016 10:22:14 AM PDT, Danny Lee <dannyl@vt.edu> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr"><span style="font-size:12.8px">Hello,</span><div style="font-size:12.8px"><br /></div><div style="font-size:12.8px">We are currently figuring out how to add GlusterFS to our system to make our systems highly available using scripts. We are using Gluster 3.7.11.</div><div style="font-size:12.8px"><br /></div><div style="font-size:12.8px"><div>Problem:</div><div>Trying to migrate to GlusterFS from a non-clustered system to a 3-node glusterfs replicated cluster using scripts. Tried various things to make this work, but it sometimes causes us to be in an indesirable state where if you call "gluster volume heal <volname> full", we would get the error message, "Launching heal operation to perform full self heal on volume <volname> has been unsuccessful on bricks that are down. Please check if all brick processes are running." All the brick processes are running based on running the command, "gluster volume status
volname"</div><div><br /></div><div>Things we have tried:</div><div><div>Order of preference</div><div>1. Create Volume with 3 Filesystems with the same data</div><div>2. Create Volume with 2 Empty filesysytems and one with the data</div><div>3. Create Volume with only one filesystem with data and then using "add-brick" command to add the other two empty filesystems</div><div>4. Create Volume with one empty filesystem, mounting it, and then copying the data over to that one. And then finally, using "add-brick" command to add the other two empty filesystems</div><div>5. Create Volume with 3 empty filesystems, mounting it, and then copying the data over</div></div><div><br /></div><div>Other things to note:</div><div> A few minutes after the volume is created and started successfully, our application server starts up against it, so reads and writes may happen pretty quickly after the volume has started. But there is only about 50MB of
data.</div></div><div style="font-size:12.8px"><br /></div><div style="font-size:12.8px">Steps to reproduce (all in a script):</div><div style="font-size:12.8px"># This is run by the primary node with the IP Adress, <server-ip-1>, that has data</div><div style="font-size:12.8px">systemctl restart glusterd<br /></div><div style="font-size:12.8px">gluster peer probe <server-ip-2></div><div style="font-size:12.8px">gluster peer probe <server-ip-3></div><div style="font-size:12.8px">Wait for "gluster peer status" to all be in "Peer in Cluster" state</div><div style="font-size:12.8px">gluster volume create <volname> replica 3 transport tcp ${BRICKS[0]} ${BRICKS[1]} ${BRICKS[2]} force<br /></div><div style="font-size:12.8px">gluster volume set <volname> nfs.disable true</div><div style="font-size:12.8px">gluster volume start <volname></div><div style="font-size:12.8px">mkdir -p $MOUNT_POINT<br /></div><div
style="font-size:12.8px">mount -t glusterfs <server-ip-1>:/volname $MOUNT_POINT</div><div style="font-size:12.8px">find $MOUNT_POINT | xargs stat</div><div style="font-size:12.8px"><br /></div><div style="font-size:12.8px">Note that, when we added sleeps around the gluster commands, there was a higher probability of success, but not 100%.</div><div style="font-size:12.8px"><br /></div><div style="font-size:12.8px"># Once volume is started, all the the clients/servers will mount the gluster filesystem by polling "mountpoint -q $MOUNT_POINT":<br /></div><div style="font-size:12.8px"><div>mkdir -p $MOUNT_POINT<br /></div><div>mount -t glusterfs <server-ip-1>:/volname $MOUNT_POINT</div></div><div style="font-size:12.8px"><br /></div><div style="font-size:12.8px">Logs:</div><div style="font-size:12.8px"><i>etc-glusterfs-glusterd.vol.log</i> in <i>server-ip-1</i></div><div style="font-size:12.8px"><i><br /></i></div><div style="font-size:12.8px"><div>[2016-06-21
14:10:38.285234] I [MSGID: 106533] [glusterd-volume-ops.c:857:__glusterd_handle_cli_heal_volume] 0-management: Received heal vol req for volume volname</div><div>[2016-06-21 14:10:38.296801] E [MSGID: 106153] [glusterd-syncop.c:113:gd_collate_errors] 0-glusterd: Commit failed on <server-ip-2>. Please check log file for details.</div></div><div style="font-size:12.8px"><br /></div><div style="font-size:12.8px"><br /></div><div style="font-size:12.8px"><i>usr-local-volname-data-mirrored-data.log</i> in <i>server-ip-1</i></div><div style="font-size:12.8px"><i><br /></i></div><div style="font-size:12.8px">[2016-06-21 14:14:39.233366] E [MSGID: 114058] [client-handshake.c:1524:client_query_portmap_cbk] 0-volname-client-0: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running.<br /></div><div style="font-size:12.8px">*I think this is caused by the self heal daemon*</div><div
style="font-size:12.8px"><br /></div><div style="font-size:12.8px"><i>cmd_history.log</i> in <i>server-ip-1</i></div><div style="font-size:12.8px"><i><br /></i></div><div style="font-size:12.8px">[2016-06-21 14:10:38.298800] : volume heal volname full : FAILED : Commit failed on <server-ip-2>. Please check log file for details.</div></div>
<p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre class="k9mail"><hr /><br />Gluster-users mailing list<br />Gluster-users@gluster.org<br /><a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>