Hi all,
The weekly bug triage is about to take place in ~30 minutes.
Meeting details:
- location: #gluster-meeting on Freenode IRC
( https://webchat.freenode.net/?channels=gluster-meeting )
- date: every Tuesday
- time: 12:00 UTC
(in your terminal, run: date -d "12:00 UTC")
Hi all,
The minutes of today's bug triage meeting:
Meeting summary
---
* agenda: https://public.pad.fsfe.org/p/gluster-bug-triage (hgowtham,
12:00:13)
* Roll Call (hgowtham, 12:00:20)
* ndevos to propose some test-cases for minimal libgfapi test
(hgowtham, 12:05:53)
*
Hi all!
I attended FOSDEM this year and was part of the team that put up the
Gluster stand. I've written up a small report on the experience at
https://kshlm.in/fosdem16/ .
I'll be writing up a report on my DevConf experience as well (soon enough).
~kaushal
On 02/12/2016 11:27 AM, Soumya Koduri wrote:
On 02/11/2016 08:33 PM, Oleksandr Natalenko wrote:
And "API" test.
I used custom API app [1] and did brief file manipulations through it
(create/remove/stat).
Then I performed drop_caches, finished API [2] and got the following
Valgrind log
On 02/13/2016 08:37 AM, Sankarshan Mukhopadhyay wrote:
> On Thu, Feb 11, 2016 at 10:38 PM, Kaushal M wrote:
>> On Thu, Feb 11, 2016 at 6:41 PM, André Bauer wrote:
>>> Already asked myself why this not exists.
>>>
>>> so... +1 from me.
>>>
>>> Regards
>>>
On Tue, Feb 16, 2016 at 6:10 AM, Kaleb KEITHLEY wrote:
>
> On 02/13/2016 08:37 AM, Sankarshan Mukhopadhyay wrote:
> > On Thu, Feb 11, 2016 at 10:38 PM, Kaushal M wrote:
> >> On Thu, Feb 11, 2016 at 6:41 PM, André Bauer wrote:
> >>>
On Tue, Feb 16, 2016 at 09:10:40AM -0500, Kaleb KEITHLEY wrote:
> On 02/13/2016 08:37 AM, Sankarshan Mukhopadhyay wrote:
> > On Thu, Feb 11, 2016 at 10:38 PM, Kaushal M wrote:
> >> On Thu, Feb 11, 2016 at 6:41 PM, André Bauer wrote:
> >>> Already asked
Hmm, OK. I've rechecked 3.7.8 with the following patches (latest
revisions):
===
Soumya Koduri (3):
gfapi: Use inode_forget in case of handle objects
inode: Retire the inodes from the lru list in inode_table_destroy
rpc: Fix for rpc_transport_t leak
===
Here is Valgrind
On Tue, Feb 16, 2016 at 06:22:58AM -0800, Amye Scavarda wrote:
> On Tue, Feb 16, 2016 at 6:10 AM, Kaleb KEITHLEY wrote:
> >
> > On 02/13/2016 08:37 AM, Sankarshan Mukhopadhyay wrote:
> > > On Thu, Feb 11, 2016 at 10:38 PM, Kaushal M wrote:
> > >> On Thu,
On Tue, Feb 16, 2016 at 6:39 AM, Niels de Vos wrote:
> On Tue, Feb 16, 2016 at 06:22:58AM -0800, Amye Scavarda wrote:
>> On Tue, Feb 16, 2016 at 6:10 AM, Kaleb KEITHLEY wrote:
>> >
>> > On 02/13/2016 08:37 AM, Sankarshan Mukhopadhyay wrote:
>> > > On Thu,
Hey Raghu,
Bitrot stub inode forget implementation (br_stub_forget()) deletes the bad
object
marker (under quarantine directory) if present. This looks incorrect as
->forget()
can be trigerred when inode table LRU size exceeeds configured limit - check bug
#1308961 which tracks this issue. I
On 02/16/2016 08:06 PM, Oleksandr Natalenko wrote:
Hmm, OK. I've rechecked 3.7.8 with the following patches (latest
revisions):
===
Soumya Koduri (3):
gfapi: Use inode_forget in case of handle objects
inode: Retire the inodes from the lru list in inode_table_destroy
rpc:
Venky,
Yes. You are right. We should not remove the quarantine entry in forget.
We have to remove it upon getting -ve lookups in bit-rot-stub and upon
getting an unlink.
I have attached a patch for it.
Unfortunately rfc.sh is failing for me with the below error.
ssh: connect to host
13 matches
Mail list logo