[Gluster-Maintainers] Update on 3.7.10 - on schedule to be tagged at 2200PDT 30th March.

[Kotresh Hiremath Ravishankar]

Inline...

----- Original Message -----
> From: "Aravinda" <avishwan at redhat.com>
> To: "Kaushal M" <kshlmster at gmail.com>, "Gluster Devel" <gluster-devel at gluster.org>, maintainers at gluster.org, "Kotresh
> Hiremath Ravishankar" <khiremat at redhat.com>
> Sent: Thursday, March 31, 2016 6:43:20 PM
> Subject: Re: [Gluster-Maintainers] Update on 3.7.10 - on schedule to be tagged at 2200PDT 30th March.
> 
> Hi Kaushal,
> 
> We have a Changelog bug which can lead to data loss if Glusterfind is
> enabled(To be specific,  when changelog.capture-del-path and
> changelog.changelog options enabled on a replica volume).
> 
> http://review.gluster.org/#/c/13861/
> 
> This is very corner case. but good to go with the release. We tried to
> merge this before the merge window for 3.7.10, but regressions not yet
> complete :(
> 
> Do you think we should wait for this patch?
> 
> @Kotresh can provide more details about this issue.

    In the above scenario, when an unlink comes on a entry, in changelog xlator, it's 'loc->pargfid'
    was getting modified to "/". So consequence is that , when it hits posix, the 'loc->pargfid' would be pointing 
    to "/" instead of actual parent. This is not so terrible yet, as we are saved by posix. Posix checks
    for "loc->path" first, only if it's not filled, it will use "pargfid/bname" combination. So only for
    clients like self-heal who does not populate 'loc->path' and the same basename exists on root, the
    unlink happens on root instead of actual path.
> 
> regards
> Aravinda
> 
> On 03/31/2016 01:29 PM, Kaushal M wrote:
> > The last change for 3.7.10 has been merged now. Commit 2cd5b75 will be
> > used for the release. I'll be preparing release-notes, and tagging the
> > release soon.
> >
> > After running verification tests and checking for any perf
> > improvements, I'll make be making the release tarball.
> >
> > Regards,
> > Kaushal
> >
> > On Wed, Mar 30, 2016 at 7:00 PM, Kaushal M <kshlmster at gmail.com> wrote:
> >> Hi all,
> >>
> >> I'll be taking over the release duties for 3.7.10. Vijay is busy and
> >> could not get the time to do a scheduled release.
> >>
> >> The .10 release has been scheduled for tagging on 30th (ie. today).
> >> In the interests of providing some heads up to developers wishing to
> >> get changes merged,
> >> I'll be waiting till 10PM PDT, 30th March. (0500UTC/1030IST 31st
> >> March), to tag the release.
> >>
> >> So you have ~15 hours to get any changes required merged.
> >>
> >> Thanks,
> >> Kaushal
> > _______________________________________________
> > maintainers mailing list
> > maintainers at gluster.org
> > http://www.gluster.org/mailman/listinfo/maintainers
> 
>