FYI..One of my patch in mainline has broken one regression test
tests/bugs/snapshot/bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t
and the fix for the same has been posted at
https://review.gluster.org/#/c/19536 . Would request some one to review
this change and merge this
On 02/10/2018 01:24 AM, Shyam Ranganathan wrote:
On 02/02/2018 10:26 AM, Ravishankar N wrote:
2) "Replace MD5 usage to enable FIPS support" - Ravi, Amar
+ Kotresh who has done most (all to be precise) of the patches listed in
https://github.com/gluster/glusterfs/issues/230 in case he would l
On 02/02/2018 10:26 AM, Ravishankar N wrote:
>>> 2) "Replace MD5 usage to enable FIPS support" - Ravi, Amar
>
> + Kotresh who has done most (all to be precise) of the patches listed in
> https://github.com/gluster/glusterfs/issues/230 in case he would like
> to add anything.
>
> There is a pendi
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-02-09-cb0339f9
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman
- Original Message -
> From: "Pranith Kumar Karampuri"
> To: "Raghavendra G"
> Cc: "Gluster Devel"
> Sent: Friday, February 9, 2018 2:30:59 PM
> Subject: Re: [Gluster-devel] Glusterfs and Structured data
>
>
>
> On Thu, Feb 8, 2018 at 12:05 PM, Raghavendra G < raghaven...@gluster.co
On Tue, Jan 30, 2018 at 3:40 AM, Shyam Ranganathan
wrote:
> Hi,
>
> I have posted an initial draft version of the release notes here [1].
>
> I would like to *suggest* the following contributors to help improve and
> finish the release notes by 06th Feb, 2017. As you read this mail, if
> you feel
On Thu, Feb 8, 2018 at 12:05 PM, Raghavendra G
wrote:
>
>
> On Tue, Feb 6, 2018 at 8:15 PM, Vijay Bellur wrote:
>
>>
>>
>> On Sun, Feb 4, 2018 at 3:39 AM, Raghavendra Gowdappa > > wrote:
>>
>>> All,
>>>
>>> One of our users pointed out to the documentation that glusterfs is not
>>> good for stor
+gluster-users
Another guideline we can provide is to disable all performance xlators for
workloads requiring strict metadata consistency (even for non gluster-block
usecases like native fuse mount etc). Note that we might still can have few
perf xlators turned on. But, that will require some e
On Wed, Feb 7, 2018 at 10:35 PM, Raghavendra G
wrote:
>
>
> On Tue, Feb 6, 2018 at 8:15 PM, Vijay Bellur wrote:
>
>>
>>
>> On Sun, Feb 4, 2018 at 3:39 AM, Raghavendra Gowdappa > > wrote:
>>
>>> All,
>>>
>>> One of our users pointed out to the documentation that glusterfs is not
>>> good for stor
