Atin Mukherjee
2015-Feb-16 04:36 UTC
[Gluster-users] "gluster volume heal info" giving wrong report
AFR team (Pranith/Ravi cced), FYA.. ~Atin On 02/13/2015 07:48 PM, Subrata Ghosh wrote:> Hi All, > > Can any one clarify the issue e , we are facing with "heal" incorrect > report mentioned below , We are using gluster 3.3.2 . > > *Issue:* > > *Bug 1039544* <https://bugzilla.redhat.com/show_bug.cgi?id=1039544> > -[FEAT] "gluster volume heal info" should list the entries that actually > required to be healed. > > *Steps to recreate* > > If we are continuously writing to a file in a volume. At the same time > if we do the following > > # gluster volume replace-bricks $vol_name $old_brick $new_brick commit > force > > # gluster volume heal $vol_name full > > #gluster volume $vol_name info --> this shows that the Numer of > files=1, even though the file is already healed. > > *Related issues:* > > http://comments.gmane.org/gmane.comp.file-systems.gluster.user/14188 > > *Fix:* > > http://review.gluster.org/#/c/7480/ > > *Query:* > > Is the fix that we are trying to back port to gluster 3.2 is the correct > code changes. > > Regards, > > Subrata > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >-- ~Atin
Subrata Ghosh
2015-Feb-21 14:14 UTC
[Gluster-users] "gluster volume heal info" giving wrong report
Hi All, Any help on this. Regards, Subrata On 02/16/2015 10:06 AM, Atin Mukherjee wrote:> AFR team (Pranith/Ravi cced), FYA.. > > ~Atin > > On 02/13/2015 07:48 PM, Subrata Ghosh wrote: >> Hi All, >> >> Can any one clarify the issue e , we are facing with "heal" incorrect >> report mentioned below , We are using gluster 3.3.2 . >> >> *Issue:* >> >> *Bug 1039544* <https://bugzilla.redhat.com/show_bug.cgi?id=1039544> >> -[FEAT] "gluster volume heal info" should list the entries that actually >> required to be healed. >> >> *Steps to recreate* >> >> If we are continuously writing to a file in a volume. At the same time >> if we do the following >> >> # gluster volume replace-bricks $vol_name $old_brick $new_brick commit >> force >> >> # gluster volume heal $vol_name full >> >> #gluster volume $vol_name info --> this shows that the Numer of >> files=1, even though the file is already healed. >> >> *Related issues:* >> >> http://comments.gmane.org/gmane.comp.file-systems.gluster.user/14188 >> >> *Fix:* >> >> http://review.gluster.org/#/c/7480/ >> >> *Query:* >> >> Is the fix that we are trying to back port to gluster 3.2 is the correct >> code changes. >> >> Regards, >> >> Subrata >> >> >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-users >>