From owner-freebsd-fs@FreeBSD.ORG Fri Jun 27 21:34:47 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB74F3E3; Fri, 27 Jun 2014 21:34:47 +0000 (UTC) Received: from mail.crittercasa.com (mail.turbofuzz.com [208.87.221.144]) by mx1.freebsd.org (Postfix) with ESMTP id 52A4A2F7F; Fri, 27 Jun 2014 21:34:47 +0000 (UTC) Received: from kruse-25.3.ixsystems.com (unknown [69.198.165.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.crittercasa.com (Postfix) with ESMTPS id BB4F316485F; Fri, 27 Jun 2014 14:27:36 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: FreeBSD support being added to GlusterFS From: Jordan Hubbard In-Reply-To: <20140627070411.GI24440@ivaldir.etoilebsd.net> Date: Fri, 27 Jun 2014 14:27:35 -0700 Message-Id: References: <6ADBB2BF-C7E8-4050-9278-2565A63D2EA8@gluster.org> <20140627070411.GI24440@ivaldir.etoilebsd.net> To: Baptiste Daroussin X-Mailer: Apple Mail (2.1878.6) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2014 21:34:47 -0000 On Jun 27, 2014, at 12:04 AM, Baptiste Daroussin = wrote: > For you information here is my version: > http://people.freebsd.org/~bapt/glusterfs.diff >=20 > It is just missing the license bits >=20 > if everyone here agrees I'll commit :) Seems reasonable. Question from my own "questions to be asked about = glusterfs" pile: Paths. I notice that glusterd requires quite a few = path not in the standard hierarchy for /usr/local (or any value of = ${prefix}) that will cause it to simply fall over upon first invocation. = To wit: /var/lib/glusterd (nothing in FreeBSD uses /var/lib at all - /var/db, = /var/run and /var/tmp are more canonical locations, depending on what = you [the service] are trying to do). In fact, ${prefix}/var seems to be generally avoided by most things in = ports. /usr/local/var/log is highly atypical, for example. This also creates problems for us in FreeNAS since our root filesystem = is read-only by default, and we simply make parts of /var (the root = /var) r/w to accommodate things wanting to write into /var/log, = /var/tmp/, /var/run and so on. I would hope that the port could also be = configured to run as a system component, or at least obey a more = predictable ${prefix} hierarchy so that we could map things suitably r/w = into the location(s) that glusterfs needs to scribble on at runtime. I was going to write all of this up in a more exhaustive email but I got = side-tracked by other projects. :) - Jordan