On Thu, May 02, 2019 at 11:04:41PM +0530, Prasanna Kalever wrote:
> Hello Gluster folks,
>
> Gluster-block team is happy to announce the v0.4 release [1].
>
> This is the new stable version of gluster-block, lots of new and
> exciting features and interesting bug fixes are made available as part
Hi
On 04/05/19 12:04 PM, Strahil wrote:
Hi Jiffin,
No vendor will support your corosync/pacemaker stack if you do not have proper
fencing.
As Gluster is already a cluster of its own, it makes sense to control
everything from there.
Best Regards,
Yeah I agree with your point. What I meant
Davide,
With release 0.4, gluster-block is now having more functionality, and we
did many stability fixes. Feel free to try out, and let us know how you
feel.
-Amar
On Fri, Nov 9, 2018 at 3:36 AM Davide Obbi wrote:
> Hi Vijay,
>
> The Volume has been created using heketi-cli blockvolume
On Thu, May 2, 2019 at 1:35 PM Prasanna Kalever wrote:
> Hello Gluster folks,
>
> Gluster-block team is happy to announce the v0.4 release [1].
>
> This is the new stable version of gluster-block, lots of new and
> exciting features and interesting bug fixes are made available as part
> of this
Thank you for the report, David. Do you have core files available on any of
the servers? If yes, would it be possible for you to provide a backtrace.
Regards,
Vijay
On Mon, May 6, 2019 at 3:09 AM David Spisla wrote:
> Hello folks,
>
> we have a client application (runs on Win10) which does
Hi,
I have problem resolving split-brain in one of my installations.
CenOS 7, glusterfs 3.10.12, replica on two nodes:
[root@ixmed1 iscsi]# gluster volume status cluster
Status of volume: cluster
Gluster process TCP Port RDMA Port Online Pid
Hello,
I create a Bug for this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1706842
Regards
David Spisla
Am Mi., 1. Mai 2019 um 14:46 Uhr schrieb Amar Tumballi Suryanarayan <
atumb...@redhat.com>:
>
>
> On Wed, Apr 17, 2019 at 1:33 PM David Spisla wrote:
>
>> Dear Gluster Community,
>>
Hello folks,
we have a client application (runs on Win10) which does some FOPs on a
gluster volume which is accessed by SMB.
*Scenario 1* is a READ Operation which reads all files successively and
checks if the files data was correctly copied. While doing this, all brick
processes crashes and in
- Original Message -
From: "David Cunningham"
To: "Ashish Pandey"
Cc: "gluster-users"
Sent: Monday, May 6, 2019 1:40:30 PM
Subject: Re: [Gluster-users] Thin-arbiter questions
Hi Ashish,
Thank you for the update. Does that mean they're now in the regular Glusterfs?
Any idea
Hi Ashish,
Thank you for the update. Does that mean they're now in the regular
Glusterfs? Any idea how long it typically takes the Ubuntu and CentOS
packages to be updated with the latest code?
On Mon, 6 May 2019 at 18:21, Ashish Pandey wrote:
> Hi,
>
> I can see that Amar has already
Hi,
I can see that Amar has already committed the changes and those are visible on
https://docs.gluster.org/en/latest/Administrator%20Guide/Thin-Arbiter-Volumes/
---
Ashish
- Original Message -
From: "Strahil"
To: "Ashish" , "David"
Cc: "gluster-users"
Sent: Saturday, May
11 matches
Mail list logo