On 05/21/2015 12:27 PM, Vijay Bellur wrote:
> On 05/21/2015 12:23 PM, Krishnan Parthasarathi wrote:
>> Smoke test has failed due to jenkins related issue. We need to
>> retrigger smoke
>> test. I am not aware of how the infrastructure works?
>>
>> Anyone, any ideas?
>>
>
> If you are logged in t
On 05/21/2015 12:23 PM, Krishnan Parthasarathi wrote:
Smoke test has failed due to jenkins related issue. We need to retrigger smoke
test. I am not aware of how the infrastructure works?
Anyone, any ideas?
If you are logged in to Jenkins, you should be able to find
Retrigger/Retrigger All li
Smoke test has failed due to jenkins related issue. We need to retrigger smoke
test. I am not aware of how the infrastructure works?
Anyone, any ideas?
- Original Message -
> Thanks for merging the patch. I have backported
> it(http://review.gluster.org/#/c/10871/) to release 3.7 branch a
Thanks for merging the patch. I have backported
it(http://review.gluster.org/#/c/10871/) to release 3.7 branch as well.
Regards,
Avra
On 05/20/2015 05:52 PM, Avra Sengupta wrote:
I've sent a patch(http://review.gluster.org/#/c/10840/) to remove this
from the test-suite. Once it get's merged I
On 05/21/2015 12:07 AM, Vijay Bellur wrote:
On 05/19/2015 11:56 PM, Vijay Bellur wrote:
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
On 05/19/2015 11:56 PM, Vijay Bellur wrote:
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. Appr
On Wed, May 20, 2015 at 06:36:49PM +0530, Atin Mukherjee wrote:
> Posted a patch [1] to fix this. I'll backport it to 3.7 once its
> accepted in mainline.
I applied to release-3.7 along with review.gluster;org/10830
and that fixes the problem.
--
Emmanuel Dreyfus
m...@netbsd.org
On 05/18/2015 08:50 PM, Atin Mukherjee wrote:
> Here is the issue:
>
> Locking on a volume fails with the following error:
>
> [2015-05-18 09:47:56.038463] E
> [glusterd-syncop.c:562:_gd_syncop_mgmt_lock_cbk] 0-management: Could not
> find peer with ID 70e65fb9-cc9d-16ba-a4f4-5fb90100
>
>
I've sent a patch(http://review.gluster.org/#/c/10840/) to remove this
from the test-suite. Once it get's merged I will re-open the clone of
this bug for 3.7.0 branch, and backport the patch.
Regards,
Avra
On 05/20/2015 12:07 PM, Krishnan Parthasarathi wrote:
No concerns.
- Original Mess
On Tue, May 19, 2015 at 8: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 su
Hi,
Recently geo-replication is enhanced to sync xattr and acls as well
from master gluster volume to slave. Geo-rep syncs data in two modes
namely using "rsync" and "tar over ssh". Syncing acls and xattrs via
rsync works fine. But using tar over ssh, there are couple of issues
syncing xattrs and
On Tuesday 19 May 2015 09:50 PM, Shyam wrote:
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 tes
12 matches
Mail list logo
