On Mon, Apr 06, 2015 at 03:10:32PM +0530, Kaushal M wrote:
The glusterfs package contains the CTR xlator, which requires libgfdb.
We have 2 choices now. We could either,
1. Move the CTR xlator into the glusterfs-server package. This makes
sense because CTR is a server side only xlator, and has
Hi All,
I have encountered this issue with the latest nightly build of glusterfs-3.7
Here is the problem with package dependency.
To install glusterfs-fuse dependency goes like this:
glusterfs-fuse -- glusterfs -- libgfdb.so
To install glusterfs-api(libgfapi) the dependency goes like this:
Hi Satheesaran,
The libgfdb was moved to glusterfs-server package via
http://review.gluster.org/#/c/9983
As per commit, libgfdb is only used by processes that run on Gluster
servers. There is
no need to have this library (and its sqlite dependency) on any system
that installs a glusterfs
The glusterfs package contains the CTR xlator, which requires libgfdb.
We have 2 choices now. We could either,
1. Move the CTR xlator into the glusterfs-server package. This makes
sense because CTR is a server side only xlator, and has no reason to
be in the glusterfs package.
or,
2. Move libgfdb
On 04/06/2015 12:45 PM, Humble Devassy Chirammal wrote:
Hi Satheesaran,
The libgfdb was moved to glusterfs-server package via
http://review.gluster.org/#/c/9983
As per commit, libgfdb is only used by processes that run on Gluster servers.
There is
no need to have this library (and its
On Mon, Apr 06, 2015 at 08:55:38AM -0400, Gaurav Garg wrote:
Hi all,
There is spurious smoke test failure in upstream master branch due to
patch http://review.gluster.org/#/c/9987/ merge.
patch http://review.gluster.org/#/c/10139/ will solve it.
Thanks! The fix has now been merged.
Any
it is possible to get around the limitations of the Phi in this area
by having an IB card in the set up and configuring Gluster to use it.
On Thu, Apr 2, 2015 at 4:10 PM, Justin Clift jus...@gluster.org wrote:
On 12 Feb 2015, at 08:54, Mohammed Rafi K C rkavu...@redhat.com wrote:
On 02/12/2015