search for: rebalan

Hi, In the past couple of weeks, we've sent the following fixes concerning VM corruption upon doing rebalance - https://review.gluster.org/#/q/status:merged+project:glusterfs+branch:master+topic:bug-1440051 These fixes are very much part of the latest 3.10.2 release. Satheesaran within Red Hat also verified that they work and he's not seeing corruption issues anymore. I'd like to hear feedback...

...i Adnan <mahdi.adnan at outlook.com> > wrote: > >> Hello, >> >> >> Yes, i forgot to upgrade the client as well. >> >> I did the upgrade and created a new volume, same options as before, with >> one VM running and doing lots of IOs. i started the rebalance with force >> and after it completed the process i rebooted the VM, and it did start >> normally without issues. >> >> I repeated the process and did another rebalance while the VM running and >> everything went fine. >> >> But the logs in the client thro...

Hi Mahdi, Did you get a chance to verify this fix again? If this fix works for you, is it OK if we move this bug to CLOSED state and revert the rebalance-cli warning patch? -Krutika On Mon, May 29, 2017 at 6:51 PM, Mahdi Adnan <mahdi.adnan at outlook.com> wrote: > Hello, > > > Yes, i forgot to upgrade the client as well. > > I did the upgrade and created a new volume, same options as before, with > one VM running and...

...om> >> wrote: >> >>> Hello, >>> >>> >>> Yes, i forgot to upgrade the client as well. >>> >>> I did the upgrade and created a new volume, same options as before, with >>> one VM running and doing lots of IOs. i started the rebalance with force >>> and after it completed the process i rebooted the VM, and it did start >>> normally without issues. >>> >>> I repeated the process and did another rebalance while the VM running >>> and everything went fine. >>> >>> But...

...gt; >>>> Hello, >>>> >>>> >>>> Yes, i forgot to upgrade the client as well. >>>> >>>> I did the upgrade and created a new volume, same options as before, >>>> with one VM running and doing lots of IOs. i started the rebalance with >>>> force and after it completed the process i rebooted the VM, and it did >>>> start normally without issues. >>>> >>>> I repeated the process and did another rebalance while the VM running >>>> and everything went fine. >>&...

...be sure it's 100% resolved. -- Respectfully Mahdi A. Mahdi ________________________________ From: Krutika Dhananjay <kdhananj at redhat.com> Sent: Tuesday, June 6, 2017 9:17:40 AM To: Mahdi Adnan Cc: gluster-user; Gandalf Corvotempesta; Lindsay Mathieson; Kevin Lemonnier Subject: Re: Rebalance + VM corruption - current status and request for feedback Hi Mahdi, Did you get a chance to verify this fix again? If this fix works for you, is it OK if we move this bug to CLOSED state and revert the rebalance-cli warning patch? -Krutika On Mon, May 29, 2017 at 6:51 PM, Mahdi Adnan <mahd...

...t; *Mahdi A. Mahdi* > > ------------------------------ > *From:* Krutika Dhananjay <kdhananj at redhat.com> > *Sent:* Tuesday, June 6, 2017 9:17:40 AM > *To:* Mahdi Adnan > *Cc:* gluster-user; Gandalf Corvotempesta; Lindsay Mathieson; Kevin > Lemonnier > *Subject:* Re: Rebalance + VM corruption - current status and request for > feedback > > Hi Mahdi, > > Did you get a chance to verify this fix again? > If this fix works for you, is it OK if we move this bug to CLOSED state > and revert the rebalance-cli warning patch? > > -Krutika > > On...