<div dir="ltr"><div>Thanks a lot, Lindsay! Appreciate the help.<br><br>It would be awesome if you could tell us whether you<br>see the issue with FUSE as well, while we get around<br>to setting up the environment and running the test ourselves.<br><br></div>-Krutika<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 20, 2016 at 2:57 AM, Lindsay Mathieson <span dir="ltr"><<a href="mailto:lindsay.mathieson@gmail.com" target="_blank">lindsay.mathieson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 20/10/2016 7:01 AM, Kevin Lemonnier wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes, you need to add a full replica set at once.<br>
I don't remember, but according to my history, looks like I've used this :<br>
<br>
gluster volume add-brick VMs host1:/brick host2:/brick host3:/brick force<br>
<br>
(I have the same without force just before that, so I assume force is needed)<br>
</blockquote>
<br></span>
Ok, I did a:<br>
<br>
gluster volume add-brick datastore1 vna.proxmox.softlog:/tank/vmda<wbr>ta/datastore1-2 vnb.proxmox.softlog:/tank/vmda<wbr>ta/datastore1-2 vng.proxmox.softlog:/tank/vmda<wbr>ta/datastore1-2<br>
<br>
I had added a 2nd windows VM as well.<br>
<br>
Looked like it was going ok for a while, then blew up. The first windows vm which was running diskmark died and won't boot. qemu-img check shows the image hopelessly corrupted. 2nd VM has also crashed and is unbootable, though qemuimg shows the qcow2 file as ok.<br>
<br>
<br>
I have a sneaking suspicion its related to active IO. VM1 was doing heavy io compared to vm2, perhaps thats while is image was corrupted worse.<br>
<br>
<br>
rebalance status looks odd to me:<br>
<br>
root@vna:~# gluster volume rebalance datastore1 status<br>
Node Rebalanced-files size scanned failures skipped status run time in h:m:s<br>
--------- ----------- ----------- ----------- ----------- ----------- ------------ --------------<br>
localhost 0 0Bytes 0 0 0 completed 0:0:1<br>
vnb.proxmox.softlog 0 0Bytes 0 0 0 completed 0:0:1<br>
vng.proxmox.softlog 328 19.2GB 1440 0 0 in progress 0:11:55<br>
<br>
<br>
Don't know why vng is taking so much longer, the nodes are identical. But maybe this normal?<br>
<br>
<br>
When I get time, I'll try again with:<br>
<br>
- all vm's shutdown (no IO)<br>
<br>
- All VM's running off the gluster fuse mount (no gfapi).<br>
<br>
<br>
cheers,<div class="HOEnZb"><div class="h5"><br>
<br>
-- <br>
Lindsay Mathieson<br>
<br>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman<wbr>/listinfo/gluster-users</a><br>
</div></div></blockquote></div><br></div>