On 05/19/2015 12:21 PM, Raghavendra Gowdappa wrote:
Yes, this is a possible scenario. There is a finite time window between,
1. Querying the size of a directory. In other words checking whether
current
write can be allowed
2. The effect of this write getting reflected in size of all the
On Tuesday 19 May 2015 06:13 AM, Shyam wrote:
On 05/18/2015 07:05 PM, Shyam wrote:
On 05/18/2015 03:49 PM, Shyam wrote:
On 05/18/2015 10:33 AM, Vijay Bellur wrote:
The etherpad did not call out, ./tests/bugs/distribute/bug-1161156.t
which did not have an owner, and so I took a stab at it
- Original Message -
From: Shyam srang...@redhat.com
To: gluster-devel@gluster.org
Sent: Tuesday, May 19, 2015 6:13:06 AM
Subject: Re: [Gluster-devel] Moratorium on new patch acceptance
On 05/18/2015 07:05 PM, Shyam wrote:
On 05/18/2015 03:49 PM, Shyam wrote:
On 05/18/2015
- Original Message -
From: Raghavendra Gowdappa rgowd...@redhat.com
To: Shyam srang...@redhat.com
Cc: gluster-devel@gluster.org
Sent: Tuesday, May 19, 2015 11:46:19 AM
Subject: Re: [Gluster-devel] Moratorium on new patch acceptance
- Original Message -
From: Shyam
- Original Message -
From: Vijay Bellur vbel...@redhat.com
To: Raghavendra Gowdappa rgowd...@redhat.com, Shyam
srang...@redhat.com
Cc: gluster-devel@gluster.org
Sent: Tuesday, May 19, 2015 1:29:57 PM
Subject: Re: [Gluster-devel] Moratorium on new patch acceptance
On 05/19/2015
Hi,
The following patch fixes an issue with readdir(p) in shard xlator:
http://review.gluster.org/#/c/10809/ whose details can be found in the commit
message.
One side effect of this is that from shard xlator, the size of the dirents list
returned to the translators above it could be
No, my suggestion was aimed at not having parallel writes. In this case quota
won't even fail the writes with EDQUOT because of reasons explained above.
Yes, we need to disable flush-behind along with this so that errors are
delivered to application.
Would conv=sync help here? That should
I just installed the Build-timeout Plugin in our Jenkins environment.
This plugin can be used to configure a timeout for jobs that take too
long to complete. There is at least one test that seems to take much
more time on occasion, and after several hours it would still not
complete:
Hi all,
This meeting is scheduled for anyone that is interested in learning more
about, or assisting with the Bug Triage.
Meeting details:
- location: #gluster-meeting on Freenode IRC
( https://webchat.freenode.net/?channels=gluster-meeting )
- date: every Tuesday
- time: 12:00 UTC
On Tue, May 19, 2015 at 4:26 PM, Jeff Darcy jda...@redhat.com wrote:
No, my suggestion was aimed at not having parallel writes. In this case
quota
won't even fail the writes with EDQUOT because of reasons explained
above.
Yes, we need to disable flush-behind along with this so that errors
After discussion with Vijaykumar mallikarjuna and other inputs in this
thread, we are proposing all quota tests to comply to following criteria:
* use dd always with oflag=append (to make sure there are no parallel
writes) and conv=fdatasync (to make sure errors, if any are delivered to
On Tue, May 19, 2015 at 5:40 PM, Raghavendra G raghaven...@gluster.com
wrote:
After discussion with Vijaykumar mallikarjuna and other inputs in this
thread, we are proposing all quota tests to comply to following criteria:
* use dd always with oflag=append (to make sure there are no parallel
* fdatasync is issued only once at the end of all writes when conv=fdatasync
* for some strange reason no fsync or fdatasync is issued at all when
conv=sync
That's because of my typo. I meant oflag=sync, not conv=sync. Sorry.
So, using conv=fdatasync in the test cannot prevent
On Tuesday 19 May 2015 05:08 PM, Niels de Vos wrote:
Hi all,
This meeting is scheduled for anyone that is interested in learning more
about, or assisting with the Bug Triage.
Meeting details:
- location: #gluster-meeting on Freenode IRC
(
On Tuesday 19 May 2015 08:36 PM, Shyam wrote:
On 05/19/2015 08:10 AM, Raghavendra G wrote:
After discussion with Vijaykumar mallikarjuna and other inputs in this
thread, we are proposing all quota tests to comply to following
criteria:
* use dd always with oflag=append (to make sure there
On 05/19/2015 08:10 AM, Raghavendra G wrote:
After discussion with Vijaykumar mallikarjuna and other inputs in this
thread, we are proposing all quota tests to comply to following criteria:
* use dd always with oflag=append (to make sure there are no parallel
writes) and conv=fdatasync (to make
Hi,
requesting someone to review the patch.
http://review.gluster.org/#/c/9893/
Regards,
Hari.
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
On 05/18/2015 08:03 PM, Vijay Bellur wrote:
On 05/16/2015 03:34 PM, Vijay Bellur wrote:
I will send daily status updates from Monday (05/18) about this so that
we are clear about where we are and what needs to be done to remove this
moratorium. Appreciate your help in having a clean set of
(Didn't see this mentioned elsewhere)
The video recordings (using a tablet resting on the desk) for
the Gluster Summit sessions in Barcelona are here:
https://www.youtube.com/channel/UCngUyL3KPYz8M2n7rDJWU0w
Thanks to Spot for providing the tablet for most of them, and
uploading them too. :)
On 05/19/2015 11:23 AM, Vijaikumar M wrote:
On Tuesday 19 May 2015 08:36 PM, Shyam wrote:
On 05/19/2015 08:10 AM, Raghavendra G wrote:
After discussion with Vijaykumar mallikarjuna and other inputs in this
thread, we are proposing all quota tests to comply to following
criteria:
* use dd
20 matches
Mail list logo
