On Mon, May 11, 2015 at 10:31:37AM +0530, Jiffin Tony Thottan wrote:
./tests/basic/mount-nfs-auth.t
Failed test: 45
Is it spurious or fails in every run?
Spurious: it passes by latest run.
--
Emmanuel Dreyfus
m...@netbsd.org
___
Gluster-devel
On Sun, May 10, 2015 at 08:29:13PM +0200, Emmanuel Dreyfus wrote:
I ran NetBSD regressions on master and I get many new failures. For
whoever is interested:
(...)
I updated the list of exlcuded tests:
tests/basic/ec
tests/basic/quota-anon-fd-nfs.t
tests/basic/tier/tier.t
tests/bugs
Hi All,
With the latest 3.7 beta1 build[1], I observed that glusterfs-server
package is dependent on glusterfs-client-xlators package.
I don't understand the dependency of server package on client package,
as I think of glusterfs-client-xlator
as the client package.
Could anyone explain on
Hi All,
There is a problem with the latest build[1], where I can create a volume
but could not start it.
As of now, it should be the packaging issue, as the issue is not found
in the master
I get the error message as volume start: test: failed: Commit failed on
localhost. Please check the
On Mon, May 11, 2015 at 08:27:50AM -0400, Meghana Madhusudhan wrote:
Hi everyone,
Please find the link to the session Highly available NFS-Ganesha server with
GlusterFS
This session is aimed to provide an overview of the active/active
NFS-Ganesha server using pacemaker/corosync.
A
On Mon, May 11, 2015 at 02:40:54PM +0530, SATHEESARAN wrote:
Hi All,
With the latest 3.7 beta1 build[1], I observed that glusterfs-server package
is dependent on glusterfs-client-xlators package.
I don't understand the dependency of server package on client package, as I
think of
On 11-05-2015 1:43, Ravishankar N wrote:
Besides, geo-replication allows to replicate a replica-1 volume in
order to achieve similar results as replica-2.
But since geo-rep uses rsync I guess that it's less optimal than
using replica-n where I guess blocks are marked as dirty to be
On 05/11/2015 10:45 PM, Christopher Pereira wrote:
On 11-05-2015 15:40, Christopher Pereira wrote:
There is an arbiter feature for replica 3 volumes
(https://github.com/gluster/glusterfs/blob/master/doc/features/afr-arbiter-volumes.md)
being released in glusterfs 3.7 which would prevent files
On Mon, May 11, 2015 at 10:03:03PM +0530, SATHEESARAN wrote:
On 05/11/2015 07:20 PM, Niels de Vos wrote:
On Mon, May 11, 2015 at 05:01:24PM +0530, SATHEESARAN wrote:
Hi All,
There is a problem with the latest build[1], where I can create a volume but
could not start it.
As of now, it
On 11-05-2015 15:40, Christopher Pereira wrote:
There is an arbiter feature for replica 3 volumes
(https://github.com/gluster/glusterfs/blob/master/doc/features/afr-arbiter-volumes.md)
being released in glusterfs 3.7 which would prevent files from going
into split-brains, you could try that
On 11-05-2015 17:57, Vijay Bellur wrote:
On 05/11/2015 10:45 PM, Christopher Pereira wrote:
On 11-05-2015 15:40, Christopher Pereira wrote:
There is an arbiter feature for replica 3 volumes
(https://github.com/gluster/glusterfs/blob/master/doc/features/afr-arbiter-volumes.md)
being
On 10-05-2015 6:26, Niels de Vos wrote:
On Sat, May 09, 2015 at 06:34:55AM -0300, Christopher Pereira wrote:
Core was generated by `glusterd --xlator-option *.upgrade=on -N'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f489c747c3b in ?? ()
[...]
Bug reported here:
This bt similar to
https://bugzilla.redhat.com/show_bug.cgi?id=1209461 . This crash due to
race between clean up thread and rpc event thread .It is known issue ,
It doesn't have any serious impact to functionality apart from creating
core dump file and log message.
for more info :
On 05/12/2015 02:15 AM, Christopher Pereira wrote:
On 11-05-2015 15:40, Christopher Pereira wrote:
There is an arbiter feature for replica 3 volumes
(https://github.com/gluster/glusterfs/blob/master/doc/features/afr-arbiter-volumes.md)
being released in glusterfs 3.7 which would prevent
On 05/11/2015 07:20 PM, Niels de Vos wrote:
On Mon, May 11, 2015 at 05:01:24PM +0530, SATHEESARAN wrote:
Hi All,
There is a problem with the latest build[1], where I can create a volume but
could not start it.
As of now, it should be the packaging issue, as the issue is not found in
the master
15 matches
Mail list logo
