Hey folks,
Wanted to check if anyone out here uses BTRFS (and willing to share
their experiences[1]) as the backend filesystem for GlusterFS. We're
planning to explore some of it's features and put it to use for
GlusterFS. This was discussed briefly during the weekly meeting on
On Thu, Sep 25, 2014 at 10:45:49AM +0530, Kiran Patil wrote:
pkill expects only one pattern, so I did as below in tests/include.rc file
and test cases started working fine.
pkill glusterfs 2/dev/null || true;
pkill glusterfsd 2/dev/null || true;
pkill glusterd 2/dev/null ||
I installed the 'psmisc' package and it installed killall command and
reverted pkill to killall in include.rc file.
Testcases started executing properly and will send tests failure report
soon.
Thanks,
Kiran.
On Thu, Sep 25, 2014 at 12:32 PM, Niels de Vos nde...@redhat.com wrote:
On Thu, Sep
Hi All,
I am happy to announce the availability of 3.6.0beta2 release for
testing. This release contains improvements in snapshot, afrv2, erasure
coding and has a few fixes for portability.
The source tarball is available at [1] and RPMs for Fedora 19,20,21,22
and RHEL/CentOS 5,6,7. are
On Thu, Sep 25, 2014 at 12:49:21PM +0530, Kiran Patil wrote:
I installed the 'psmisc' package and it installed killall command and
reverted pkill to killall in include.rc file.
Testcases started executing properly and will send tests failure report
soon.
Thanks, I've added 'psmisc' to the
hi , Dear experts of gluster,
today I have met a problem. I install glusterfs 3.6 beta1 at
client , and mount a volume which
servered by glusterfs 3.3 server, the mount operation success. And I can
read file successfully. But
write operation will failed with error E72 Close error on
FYI,
This run done on the 3.6 branch.
To fix these Coverity issues , please check the below link for guidelines:
http://www.gluster.org/community/documentation/index.php/Fixing_Issues_Reported_By_Tools_For_Static_Code_Analysis#Coverity
Thanks,
Lala
Original Message
Subject:
The below testcases failing are related to xfs, cluster and others..
The hardcoded ones I have fixed temporarily by providing the absolute
pathname.
Testcase /tests/bugs/bug-767095.t is fixed by changing awk parameter $5 to
$4.
Testcase tests/bugs/bug-861542.t is failing at EXPECT N/A
All,
I have 2 Ubuntu 13.10 nodes (gluster 3.2.7) with local gluster volumes set to
mirror (two webservers keeping their content in sync with one another). I
upgraded one node to 14.04.1 (gluster 3.4.2). After rebooting, Gluster can't
find my volumes. gluster volume status returns No volumes
hi , Dear experts of gluster,
today I have met a problem. I install glusterfs 3.6 beta1 at
client , and mount a volume which
servered by glusterfs 3.3 server, the mount operation success. And I can
read file successfully. But
write operation will failed with error E72 Close error on
(sorry for replying to own email here, but in case someone else is having these
issues)
The immediate issue here is that the Ubuntu package moved its configuration
location from /etc/glusterd to /var/lib/glusterd. Editing
/etc/glusterfs/glusterd.vol to point it back to /etc/glusterd at least
3.2 is not able to connect with any other version.
Follow these upgrade instructions which are valid for upgrading from 3.2 to 3.4
also:
http://vbellur.wordpress.com/2012/05/31/upgrading-to-glusterfs-3-3/
On September 25, 2014 7:23:46 AM PDT, Brantley Hobbs bho...@itos.uga.edu
wrote:
All,
Thanks Joe.
Since these are local volumes with replicated peers, is it possible to break
the peering, upgrade them one at a time and then re-peer?
Thanks!
From: Joe Julian [mailto:j...@julianfamily.org]
Sent: Thursday, September 25, 2014 10:45 AM
To: Brantley Hobbs; Gluster-users@gluster.org
On 25/09/2014, at 2:31 PM, Kiran Patil wrote:
The below testcases failing are related to xfs, cluster and others..
The hardcoded ones I have fixed temporarily by providing the absolute
pathname.
Testcase /tests/bugs/bug-767095.t is fixed by changing awk parameter $5 to $4.
Interesting.
Justin Clift jus...@gluster.org wrote:
Emmanuel Dreyfus and Harsha may have useful insight here too. They're
been working through the regression scripts for a while now, making them
more cross platform in order to run on the BSD's. (and maybe OSX
eventually)
Sure but what it the question?
Hi all,
I had an instance of heal-failed today on a 3x2 replicated volume with 17TB on
ubuntu 12.04 xfs bricks running gluster 3.5.2
Initially:
on the brick log:
Warnings in
Hi all,
I had an instance of heal-failed today on a 3x2 replicated volume with 17TB on
ubuntu 12.04 xfs bricks running gluster 3.5.2
Initially:
on the brick log:
Warnings in
On 25/09/2014, at 6:47 PM, Emmanuel Dreyfus wrote:
Justin Clift jus...@gluster.org wrote:
Emmanuel Dreyfus and Harsha may have useful insight here too. They're
been working through the regression scripts for a while now, making them
more cross platform in order to run on the BSD's. (and
On 09/24/2014 06:48 PM, Justin Clift wrote:
On 24/09/2014, at 2:07 PM, Kiran Patil wrote:
Some of the reasons I have found so far are as below,
1. Cleanup operation does not work since killall is not part of CentOS 7
2. I used pkill and still testcases fail at first step Ex: TEST glusterd
On 25/09/2014, at 9:28 PM, Lalatendu Mohanty wrote:
snip
Have we published somewhere which distributions or OS versions we are running
regression tests ? if not lets compile it and publish as this will help
community to understand which os distributions are part of the regression
testing.
Justin Clift jus...@gluster.org wrote:
Seems to be some portability issues in the regression tests for
CentOS 7 too. Figured you might have some insight into some of
them, since you're doing portability stuff around this anyway. :)
Start of thread:
(...)
It seems very broken!
I would
21 matches
Mail list logo
