From owner-freebsd-fs@FreeBSD.ORG Sun Aug 17 04:09:27 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D852581F for ; Sun, 17 Aug 2014 04:09:27 +0000 (UTC) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90E202192 for ; Sun, 17 Aug 2014 04:09:26 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id i8so3590447qcq.41 for ; Sat, 16 Aug 2014 21:09:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EAC9MiuQuA78EkG8BqOkn7zpgfSsA6OBHQY6x7vdEG8=; b=GoBB2dNxwUBRtRMcEFQ9NCCgmdv752c4sx838hW1OZGKt4nP2+hI6vGcIVBEMluR4Z 0QVUhG7JtRU2gDEifwIlT8PQDqSLV1C8S6BV6tnK2heWZeqEppt6vBuF5N0+MlWvVAJJ gkE51pFjxljTSNJCu5imszADVLn2MNinQOK18ZzWeD+dZs5dkYsP1pB21FODOnlCgH81 sKW2TNFG3syGPbsnzA+8iBYEoqYo0uHm+xftub59EfomLoQCdoHqFNSrDmC2SHtvYPto UBIWUf8XpJ4/OtYODQN1HvGqAVBMm+arNoAtCHcrl2Dn0XBNVCt3hondVLM5wKwx5JHG gbjQ== X-Gm-Message-State: ALoCoQmztaMW8oHrX4SuGy49QIQx7B//rPXy6Ti7g8Mu+cGlgfExObOy5Kb9CTV0knfoC3viXCNS MIME-Version: 1.0 X-Received: by 10.140.48.234 with SMTP id o97mr41429843qga.10.1408248112069; Sat, 16 Aug 2014 21:01:52 -0700 (PDT) Received: by 10.229.213.129 with HTTP; Sat, 16 Aug 2014 21:01:51 -0700 (PDT) X-Originating-IP: [73.189.167.30] In-Reply-To: <2F416D06-0A98-4E66-902C-ED0690A4B1C0@ixsystems.com> References: <6ADBB2BF-C7E8-4050-9278-2565A63D2EA8@gluster.org> <20140627070411.GI24440@ivaldir.etoilebsd.net> <0F20AEEC-6244-42BC-815C-1440BBBDE664@mail.turbofuzz.com> <20140629203746.GI34108@ivaldir.etoilebsd.net> <1A58F492-946F-46D4-A19E-2734F368CDAC@mail.turbofuzz.com> <0ABAE2AC-BF1B-4125-ACA9-C6177D013E25@mail.turbofuzz.com> <20140706230910.GA8523@ivaldir.etoilebsd.net> <2F416D06-0A98-4E66-902C-ED0690A4B1C0@ixsystems.com> Date: Sat, 16 Aug 2014 21:01:51 -0700 Message-ID: Subject: Re: FreeBSD support being added to GlusterFS From: Harshavardhana To: Jordan Hubbard Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Aug 2014 04:09:27 -0000 On Sat, Aug 16, 2014 at 7:57 PM, Jordan Hubbard wrote: > Thanks! Just to make sure I understand for our own ports repo in FreeNAS= -land: > > 1. You have updated the tarball but Baptiste is still maintaining the por= t, correct? > This i have no idea, i saw two people providing the 'shar' file so i guessed both of them were working on it. > If Baptiste would like someone else to take it over, I can probably coax = one of our resident committers to do it as well. We frankly have not been = able to do any testing of glusterfs in FreeNAS yet since glusterd just catc= hes a signal 10 whenever any glusterfs operation is performed. Since this = is also really early BETA software, I figured the FreeBSD port was still a = bit green and I'd simply wait for it to get a bit more mature. Now that yo= u say you=E2=80=99ve gotten a regression suite up and running, I=E2=80=99m = guessing the time to really push on it in FreeNAS 9.3-ALPHA is probably soo= n? > Do you know the issue of Signal 10? - can see the logs and verify them, I have been able to run lot of tests myself - but most of it is in FreeBSD 10.0. Currently every patch submitted for GlusterFS are being smoke tested on FreeBSD and NetBSD through Jenkins CI (for compile consistency), gearing up for final regression suite compatibility. This tarball was from the master branch which has all the necessary fixes, adding to that recently we made a 'release-3.6' branch gearing up for GlusterFS 3.6.0 which would have FreeBSD support - there is one patch which is still missing from release-3.6 i.e moving off /var/lib/glusterd ---> /var/db/glusterd on non Linux platforms, which is was ported from master recently and currently under review. I have gotten bits and pieces of regression tests running, the real hurdle has been to get the pidof, pgrep functionalities right and the pidof provided in 'sysutils' seems to be not working properly. Using pgrep works for some cases and miserably fails on others. NetBSD maintainer for GlusterFS made - http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/pidof/ - out of sysvinit Linux package, after battling the same issues - which i think should resolve those problems on FreeBSD as well, but i haven't gotten around getting it ported/tested. If some one is interested we can get the existing FreeBSD port of pidof deprecated. Another issue i saw was FUSE related which lacked FOPEN_DIRECT_IO support for which i submitted a patch yesterday to get GlusterFS internal "meta" module working, here is the relevant PR - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192701 > 2. That said, it also sounds like updating the glusterfs port is going to= have to wait for your cmockery2 port to get accepted and committed to the = tree, since otherwise it won=E2=80=99t build - is that a correct assessment= ? > That is a correct assesment, but Cmockery2 is "patch ready" here - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192420 - just needs to be pushed in if there are no other issues. Let me know if you have further questions. Thanks --=20 Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes