On Wed, Apr 06, 2016 at 04:32:40PM -0400, Glomski, Patrick wrote:
> We run gluster 3.7 in a distributed replicated setup. Infiniband (tcp)
> links the gluster peers together and clients use the ethernet interface.
>
> This setup is stable running CentOS 6.x and using the most recent
> infiniband d
I've been trying to figure out what's causing CentOS regression tests to
fail with core dumps, quite clearly unrelated to the patches that are
being affected. I've managed to find a couple of clues, so it seems
that maybe someone else will recognize something and zero in on the
problem faster than
Upon further investigation, I've been able to determine that the problem
lies in this line of our generic cleanup routine.
type cleanup_lvm &>/dev/null && cleanup_lvm || true;
This works great if snapshot.rc we're at the end of a test that included
snapshot.rc (which defines cleanup_lvm),
Hey Pranith, Ashish -
We have broken support for group virt after the following commit in
release-3.7:
commit 46920e3bd38d9ae7c1910d0bd83eff309ab20c66
Author: Ashish Pandey
Date: Fri Mar 4 13:05:09 2016 +0530
cluster/ec: Provide an option to enable/disable eager lock
I have sent a pa
On Sat, Apr 9, 2016 at 2:05 AM, Jeff Darcy wrote:
> Upon further investigation, I've been able to determine that the problem
> lies in this line of our generic cleanup routine.
>
> type cleanup_lvm &>/dev/null && cleanup_lvm || true;
>
> This works great if snapshot.rc we're at the end of
On 04/09/2016 07:55 AM, Vijay Bellur wrote:
Hey Pranith, Ashish -
We have broken support for group virt after the following commit in
release-3.7:
Just nit-picking, eager-lock is ON by default for replicate volumes, so
it is not a deal breaker unless some one explicitly disables the option
-Atin
Sent from one plus one
On 09-Apr-2016 9:32 am, "Rajesh Joseph" wrote:
>
>
>
> On Sat, Apr 9, 2016 at 2:05 AM, Jeff Darcy wrote:
>>
>> Upon further investigation, I've been able to determine that the problem
>> lies in this line of our generic cleanup routine.
>>
>> type cleanup_lvm
On 04/09/2016 12:15 AM, Ravishankar N wrote:
Just nit-picking, eager-lock is ON by default for replicate volumes, so
it is not a deal breaker unless some one explicitly disables the option
before enabling the virt-profile settings.
I am aware of this. The problem however is in applying profile
On 04/09/2016 09:52 AM, Vijay Bellur wrote:
based on workflow decisions in oVirt, we might even have the volume
being marked as unavailable for virtual machine image storage
Ah, did not know this. Blocker it is indeed, then.
-Ravi
___
Gluster-devel ma
On 04/09/2016 12:17 AM, Atin Mukherjee wrote:
-Atin
Sent from one plus one
On 09-Apr-2016 9:32 am, "Rajesh Joseph" mailto:rjos...@redhat.com>> wrote:
>
>
>
> On Sat, Apr 9, 2016 at 2:05 AM, Jeff Darcy mailto:jda...@redhat.com>> wrote:
>>
>> Upon further investigation, I've been able to dete
10 matches
Mail list logo