search for: libglusterfsclient

...stribute: on subvolume '192.168.1.127-1': avail_percent is: 96.00 and avail_space is: 66246918144 [2010-03-04 13:48:16] D [dht-diskusage.c:71:dht_du_info_cbk] distribute: on subvolume '192.168.1.128-1': avail_percent is: 97.00 and avail_space is: 67548491776 [2010-03-04 13:48:16] D [libglusterfsclient.c:1744:libgf_vmp_map_ghandle] libglusterfsclient: New Entry: /nfs/NAS [2010-03-04 13:48:16] D [libglusterfsclient.c:1487:libgf_init_vmpentry] libglusterfsclient: New VMP entry: /nfs/NAS [2010-03-04 13:48:16] D [libglusterfsclient.c:1755:libgf_vmp_map_ghandle] libglusterfsclient: Empty list [2010-03...

...=/ was to make sure that the default paths for configuration and log files are /etc/glusterfs and /var/log/glusterfs. When i try to run make install I get the following error: test -z "//lib" || mkdir -p -- "//lib" /bin/sh ../../libtool --mode=install /usr/bin/install -c 'libglusterfsclient.la' '//lib/libglusterfsclient.la' libtool: install: error: cannot install `libglusterfsclient.la' to a directory not ending in /usr/lib make[3]: *** [install-libLTLIBRARIES] Error 1 make[3]: Leaving directory `/root/admin/glusterfs/build/glusterfs-1.4.0rc7/libglusterfsclient/src'...

I am trying to build the latest release candidate and have run into a bit of a problem. When I run ./configure, I get: GlusterFS configure summary =========================== FUSE client : no Infiniband verbs : no epoll IO multiplex : yes Berkeley-DB : no libglusterfsclient : yes mod_glusterfs : no () argp-standalone : no I am going to need the gluster FUSE client now and ibverbs support in the near future. What's the correct incantation? Thanks! -- Matt

Hi all, I'm very happy to see the release of 3.3.0. One of the features I was waiting for are striped replicated volumes. We plan to store KVM images (from a OpenStack installation) on it. I read through the docs and found the following phrase: "In this release, configuration of this volume type is supported only for Map Reduce workloads." What does that mean exactly? Hopefully not,

Hi all, I'm currently in the process of testing a Gluster 3.0.0 setup (4 nodes, 2 servers, 2 clients, client-side replication), and have run into the occasional hiccup (and at least one big crash). Unfortunately, the logged remnants of these incidents leave something to be desired, and as anyone who's tried to track down a crash knows, the more log data you have, the better. Thus,