FreeBSD support being added to GlusterFS

[Jordan Hubbard]

On Jul 6, 2014, at 12:12 AM, Harshavardhana <harsha at harshavardhana.net> wrote:

> Just tested this on FreeBSD 10 after 'rm -rf /usr/local' and complete
> GlusterFS recompile/install - glusterd doesn't indicate this issue. A
> dummy directory "/usr/local/var/log/glusterfs" directory is created
> nevertheless after a 'make install'
> 
> glusterfsd/src/Makefile.am:     $(INSTALL) -d -m 755
> $(DESTDIR)$(localstatedir)/log/glusterfs
> 
> ^^ this should take care of the problematic directory.
> 
> Can you check if 'ls -l /usr/local/var/log' exists? as a work-around
> you can compile with

I can make the /usr/local/var/log/glusterfs directory and it gets much further.   That said, is there some special configure flags we should be passing in our version of the port to properly stuff glusterfs into /var instead?  Your email tends to imply that we should be passing —localstatedir, which we can certainly do no problem, I’m just wondering if that’s your long-term plan.  Again, this is our port:  https://github.com/freenas/ports/tree/freenas/9-stable/sysutils/glusterfs

The fundamental issue with /usr/local is, again, that /usr/local is read-only on FreeNAS.  If there are configuration files that glusterfs expects to be modifiable, they can’t live anywhere in /usr/local, nor of course can any temporary files or log files.  We have made special provisions for /etc and /var such that those can be modified, so we basically just need to compile gluster as a “system service” and put it in the system directories (e.g. prefix is /, not /usr/local).

Thanks - I think we’re getting closer!  Now that glusterd is actually running, I just need to figure out how to test it. :)

- Jordan