On Thursday, February 12, 2015 at 10:40:52 AM UTC+1, Stephan Duehr wrote: > There's no separate repository, the gfapi storage backend is in the direcotory > src/stored/backends of the repository https://github.com/bareos/bareos > > You'll need to compile everything, look for "Howto compile" in > http://www.bareos.org/en/howto-contribute.html > but as you'll probably build for 14.2, look for configure options > at https://github.com/bareos/bareos/blob/bareos-14.2/debian/rules > > If using Bareos 14.2 packages, you must also do > git checkout origin/bareos-14.2 > after git clone https://github.com/bareos/bareos.git > > If all worked well, you'll find > libbareossd-gfapi-14.2.2.so > that must be copied to /usr/lib/bareos/backends/ > and there must be the symlink created: > ln -s libbareossd-gfapi libbareossd-gfapi-14.2.2.so
Thanks for the pointer to the documentation. I followed these instructions and unfortunately it looks like the configure does not find Gluster's header files, here is an extract of the config.log file: | #include <api/glfs.h> configure:31521: result: no configure:31521: checking api/glfs.h presence configure:31521: gcc -E -g -O2 conftest.c conftest.c:207:22: fatal error: api/glfs.h: No such file or directory I used the following configure parameters based on the 14.2 Debian rules file: CONFIGURE_COMMON="--with-sbin-perm=755 --libdir=/usr/lib/bareos --sysconfdir=/etc/bareos --with-archivedir=/var/lib/bareos/storage --with-backenddir=/usr/lib/bareos/backends -- with-configtemplatedir=/usr/lib/bareos/defaultconfigs --with-scriptdir=/usr/lib/bareos/scripts --with-plugindir=/usr/lib/bareos/plugins --with-working-dir=/var/lib/bareos --wit h-pid-dir=/var/lib/bareos --with-bsrdir=/var/lib/bareos --with-logdir=/var/log/bareos --with-subsys-dir=/var/lock --enable-smartalloc --disable-conio --enable-readline --enable -batch-insert --enable-dynamic-debian-package-list --enable-dynamic-cats-backends --enable-dynamic-storage-backends --enable-acl --enable-xattr --enable-scsi-crypto --enable-lm db --enable-ndmp --enable-ipv6 --with-postgresql --with-mysql --with-sqlite3 --with-tcp-wrappers --with-openssl --with-glusterfs=/usr/include/glustserfs --with-dir-user=$DIRECT OR_DAEMON_USER --with-dir-group=$DAEMON_GROUP --with-sd-user=$STORAGE_DAEMON_USER --with-sd-group=$STORAGE_DAEMON_GROUP --with-fd-user=$FILE_DAEMON_USER --with-fd-group=$DAEMON _GROUP --with-dir-password="XXX_REPLACE_WITH_DIRECTOR_PASSWORD_XXX" --with-fd-password="XXX_REPLACE_WITH_CLIENT_PASSWORD_XXX" --with-sd-password="XXX_REPLACE_WITH_STORAGE_PASSW ORD_XXX" --with-mon-dir-password="XXX_REPLACE_WITH_DIRECTOR_MONITOR_PASSWORD_XXX" --with-mon-fd-password="XXX_REPLACE_WITH_CLIENT_MONITOR_PASSWORD_XXX" --with-mon-sd-password= "XXX_REPLACE_WITH_STORAGE_MONITOR_PASSWORD_XXX" --with-basename="XXX_REPLACE_WITH_LOCAL_HOSTNAME_XXX" --with-hostname="XXX_REPLACE_WITH_LOCAL_HOSTNAME_XXX" --enable-includes -- disable-rpath" Note here that I added --with-glusterfs=/usr/include/glustserfs for Glustser. I am using the official Gluster 3.5 Debian repository for wheezy and installed the glusterfs-client and glusterfs-server packages. You have any ideas what I am doing wrong here? > Although any should work by using gluster fuse mount, better performance is > expected by > native gfapi access due to less overhead than fuse. Mounting a GlusterFS volume using FUSE is simply horrible, you do not want to do that to yourself or anyone... Performance is a disaster. You can watch the context switches on your machine going nuts during a simple file copy, never saw that before. You definitely want to use API access and avoid FUSE by all means. NFS is not so much better neither except that it handles a large amount of small files slightly better. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
