<html><body><div style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000000"><div>Also could you please attach glustershd.log files and the client logs?<br></div><div><br></div><div>-Krutika<br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;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;" data-mce-style="border-left: 2px solid #1010FF; 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;"><b>From: </b>"Krutika Dhananjay" <kdhananj@redhat.com><br><b>To: </b>"Lindsay Mathieson" <lindsay.mathieson@gmail.com><br><b>Cc: </b>"gluster-users" <Gluster-users@gluster.org><br><b>Sent: </b>Thursday, January 21, 2016 10:14:34 AM<br><b>Subject: </b>Re: [Gluster-users] File Corruption when adding bricks to live replica volumes<br><div><br></div><div style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000000" data-mce-style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000000;"><div>It should not, especially if you followed the steps I gave in my previous mail.<br></div><div>Just to be clear, how did you clean up the brick that was removed? I mean, what command did you use?<br></div><div><br></div><div>-Krutika<br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;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;" data-mce-style="border-left: 2px solid #1010FF; 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;"><b>From: </b>"Lindsay Mathieson" <lindsay.mathieson@gmail.com><br><b>To: </b>"Krutika Dhananjay" <kdhananj@redhat.com><br><b>Cc: </b>"gluster-users" <Gluster-users@gluster.org><br><b>Sent: </b>Thursday, January 21, 2016 6:24:58 AM<br><b>Subject: </b>Re: [Gluster-users] File Corruption when adding bricks to live replica volumes<br><div><br></div>On 19/01/16 22:06, Krutika Dhananjay wrote:<br>> As far as the reverse heal is concerned, there is one issue with <br>> add-brick where replica count is increased, which is still under review.<br>> Could you instead try the following steps at the time of add-brick and <br>> tell me if it works fine:<br>><br>> 1. Run 'gluster volume add-brick datastore1 replica 3 <br>> vng.proxmox.softlog:/vmdata/datastore1' as usual.<br>><br>> 2. Kill the glusterfsd process corresponding to newly added brick (the <br>> brick in vng in your case). You should be able to get its pid in the <br>> output of 'gluster volume status datastore1'.<br>> 3. Create a dummy file on the root of the volume from the mount point. <br>> This can be any random name.<br>> 4. Delete the dummy file created in step 3.<br>> 5. Bring the killed brick back up. For this, you can run 'gluster <br>> volume start datastore1 force'.<br>> 6. Then execute 'gluster volume heal datastore1 full' on the node with <br>> the highest uuid (this we know how to do from the previous thread on <br>> the same topic).<br>><br>> Then monitor heal-info output to track heal progress.<br><div><br></div><br>I'm afraid it didn't work Krutika, I still got the reverse heal problem.<br><div><br></div>nb. I am starting from a replica 3 store, removing a brick, cleaning it, <br>then re-adding it. Possibly that affects the process?<br><div><br></div>-- <br>Lindsay Mathieson<br><div><br></div></blockquote><div><br></div></div><br>_______________________________________________<br>Gluster-users mailing list<br>Gluster-users@gluster.org<br>http://www.gluster.org/mailman/listinfo/gluster-users</blockquote><div><br></div></div></body></html>