On Thu, Aug 11, 2016 at 12:14 PM, Kaushal M wrote:
> Hi all,
>
> As you know, 3.6 will be EOLed once 3.9 is released. But we still have
> a lot of bugs open on 3.6.x [1]. We need to screen these bugs and
> close/clone these as required.
>
> In yesterday's community meeting, we decided to have thi
On Thu, Aug 11, 2016 at 11:07:22AM +0530, Nigel Babu wrote:
> I'd like to propose renaming them to:
> * centos-regression
> * netbsd-regression
I suggest you keep an OS version number;
netbsd7-regression
That way we can introduce an OS update as experimental without breaking
what is known to wor
On Thu, Aug 11, 2016 at 12:14:34PM +0530, Kaushal M wrote:
> Hi all,
>
> As you know, 3.6 will be EOLed once 3.9 is released. But we still have
> a lot of bugs open on 3.6.x [1]. We need to screen these bugs and
> close/clone these as required.
>
> In yesterday's community meeting, we decided to
On Thu, Aug 11, 2016 at 07:19:10AM +, Emmanuel Dreyfus wrote:
> On Thu, Aug 11, 2016 at 11:07:22AM +0530, Nigel Babu wrote:
> > I'd like to propose renaming them to:
> > * centos-regression
> > * netbsd-regression
>
> I suggest you keep an OS version number;
> netbsd7-regression
>
> That way
On Thu, Aug 11, 2016 at 12:20:56PM +0530, Kaushal M wrote:
> On Thu, Aug 11, 2016 at 11:07 AM, Nigel Babu wrote:
> > Hello folks,
> >
> > Our regression jobs are currently named the following:
> >
> > * rackspace-regression-2GB-triggered
> > * rackspace-netbsd7-regression-triggered
> >
> > I'd lik
On Thu, Aug 11, 2016 at 4:29 PM, Serkan Çoban wrote:
> I can wait for the patch to complete, please inform me when you ready.
> If it will take too much time to solve the crawl issue I can test
> without it too...
>
I don't know the Root cause for the problem, so I am not sure by when it
will be
I can wait for the patch to complete, please inform me when you ready.
If it will take too much time to solve the crawl issue I can test
without it too...
Serkan
On Thu, Aug 11, 2016 at 5:52 AM, Pranith Kumar Karampuri
wrote:
>
>
> On Wed, Aug 10, 2016 at 1:58 PM, Serkan Çoban wrote:
>>
>> Hi,
The Red Hat Gluster Storage documentation team and I had a conversation
about how we can our upstream documentation more consistent and improved
for our users, and they're willing to work with us to find where the major
gaps are in our documentation. This is awesome! But it's going to take some
wor
On Thu, Aug 11, 2016 at 4:47 AM, Niels de Vos wrote:
> On Thu, Aug 11, 2016 at 07:19:10AM +, Emmanuel Dreyfus wrote:
>> On Thu, Aug 11, 2016 at 11:07:22AM +0530, Nigel Babu wrote:
>> > I'd like to propose renaming them to:
>> > * centos-regression
>> > * netbsd-regression
>>
>> I suggest you k
On Sat, Aug 6, 2016 at 7:37 AM, Niels de Vos wrote:
> Hi,
>
> As *we* all are aware, striped volumes should not be used anymore. The
> replacement for this is sharding, available and stable since the latest
> 3.7 releases and 3.8. Unfortunately users still create striped volumes,
> and some even w
On Thu, Aug 11, 2016 at 11:34:24PM -0400, Vijay Bellur wrote:
> On Thu, Aug 11, 2016 at 4:47 AM, Niels de Vos wrote:
> > On Thu, Aug 11, 2016 at 07:19:10AM +, Emmanuel Dreyfus wrote:
> >> On Thu, Aug 11, 2016 at 11:07:22AM +0530, Nigel Babu wrote:
> >> > I'd like to propose renaming them to:
>
On Thu, Aug 11, 2016 at 12:20:56PM +0530, Kaushal M wrote:
> On Thu, Aug 11, 2016 at 11:07 AM, Nigel Babu wrote:
> > Hello folks,
> >
> > Our regression jobs are currently named the following:
> >
> > * rackspace-regression-2GB-triggered
> > * rackspace-netbsd7-regression-triggered
> >
> > I'd lik
On Thu, Aug 11, 2016 at 9:31 AM, Raghavendra G
wrote:
> Couple of more areas to explore:
> 1. purging kernel dentry and/or page-cache too. Because of patch [1],
> upcall notification can result in a call to inode_invalidate, which results
> in an "invalidate" notification to fuse kernel module. W
On Tue, Aug 09, 2016 at 03:44:43PM +0530, Nigel Babu wrote:
> Hello,
>
> Here are the netbsd regressions for the last 2 weeks. Please let me know if
> there are infra issues particularly in nbslave7h. As far as I can see, it
> just gets assigned more jobs than other machines, and hence more failure
Hi,
As you may probably know meta xlators provide a /proc kind of virtual
name space that can be used to get meta data information for mount
process. We are trying to enhance the meta xlator to support more
features and to support other protocols.
Currently meta generate gfid by its own and store
On 08/12/2016 11:29 AM, Mohammed Rafi K C wrote:
Hi,
As you may probably know meta xlators provide a /proc kind of virtual
name space that can be used to get meta data information for mount
process. We are trying to enhance the meta xlator to support more
features and to support other protocols.
On 08/12/2016 11:48 AM, Ravishankar N wrote:
> On 08/12/2016 11:29 AM, Mohammed Rafi K C wrote:
>> Hi,
>>
>> As you may probably know meta xlators provide a /proc kind of virtual
>> name space that can be used to get meta data information for mount
>> process. We are trying to enhance the meta xl
17 matches
Mail list logo
