Glad the fixes worked for you. Thanks for that update!
-Krutika
On Tue, Aug 2, 2016 at 7:31 PM, David Gossage
wrote:
> So far both dd commands that failed previously worked fine on 3.7.14
>
> Once I deleted old content from test volume it mounted to oVirt via
>
On Tue, Aug 2, 2016 at 8:21 PM, Vijay Bellur wrote:
> On 08/02/2016 07:27 AM, Aravinda wrote:
>
>> Hi,
>>
>> As many of you aware, Gluster Eventing feature is available in Master.
>> To add support to listen to the Events from GlusterFS Clients following
>> changes are
Ah, that's an edge case. Retrigger them. I think as a future note, if
you're going to edit the commit or do a no-op rebase, do it after your
regression results are in.
On Tue, Aug 2, 2016 at 8:22 PM, Pranith Kumar Karampuri wrote:
> hi Nigel,
>When we rebase the
hi Nigel,
When we rebase the patch by just changing the
commit-message/description it rightly doesn't re-trigger the regression,
but the regression results are still coming for patchset before rebase so
the +1s are not appearing. You can see http://review.gluster.org/#/c/15070/
as an
On 08/02/2016 07:27 AM, Aravinda wrote:
Hi,
As many of you aware, Gluster Eventing feature is available in Master.
To add support to listen to the Events from GlusterFS Clients following
changes are identified
- Change in Eventsd to listen to tcp socket instead of Unix domain
socket. This
On Tue, Aug 2, 2016 at 6:01 AM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> On 2/08/2016 5:07 PM, Kaushal M wrote:
>
>> GlusterFS-3.7.14 has been released. This is a regular minor release.
>> The release-notes are available at
>>
>>
So far both dd commands that failed previously worked fine on 3.7.14
Once I deleted old content from test volume it mounted to oVirt via storage
add when previously it would error out. I am now creating a test VM with
default disk caching settings (pretty sure oVirt is defaulting to none
rather
On Tue, Aug 2, 2016 at 4:57 PM, Aravinda wrote:
> Hi,
>
> As many of you aware, Gluster Eventing feature is available in Master. To
> add support to listen to the Events from GlusterFS Clients following
> changes are identified
>
> - Change in Eventsd to listen to tcp socket
Hi,
As many of you aware, Gluster Eventing feature is available in Master.
To add support to listen to the Events from GlusterFS Clients following
changes are identified
- Change in Eventsd to listen to tcp socket instead of Unix domain
socket. This enables Client to send message to Eventsd
Hi all,
The weekly Gluster bug triage is about to take place in an hour
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
On Sat, Jul 30, 2016 at 5:26 AM, Jonathan Holloway wrote:
[snip]
> I've posted several videos on YouTube at the following links.
> There are eight sections and then a combined full-length (really full)
> video.
> There is a little bit of Unit Test covered in "3. Using
These emails really need manual verification of the bugs it complains
about. This is an example that is incorrect:
> 1302149 (mainline) NEW: Add support for SEEK_DATA/SEEK_HOLE to stripe
> [master] I9cfed7 stripe: add seek() FOP as not supported (MERGED)
> ** nde...@redhat.com: Bug 1302149
GlusterFS-3.7.14 has been released. This is a regular minor release.
The release-notes are available at
https://github.com/gluster/glusterfs/blob/release-3.7/doc/release-notes/3.7.14.md
.
Binary packages have been built for different distributions. A big
thank you to Neils and Kaleb for the very
1279747 (mainline) MODIFIED: spec: add CFLAGS=-DUSE_INSECURE_OPENSSL to
configure command-line for RHEL-5 only
** mchan...@redhat.com: No change posted, but bug 1279747 is in MODIFIED **
1338593 (mainline) ASSIGNED: clean posix locks based on client-id as part of
server_connection_cleanup
14 matches
Mail list logo