Date: Fri, 8 Jan 2016 08:32:31 -0600 (CST) From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us> To: Freddie Cash <fjwcash@gmail.com> Cc: John Case <case@sdf.org>, FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: Re: Solaris 11 ZFS send to FreeBSD 10.2 ... Message-ID: <alpine.GSO.2.01.1601080828550.28454@freddy.simplesystems.org> In-Reply-To: <CAOjFWZ5tGnNxQ5oYVW-%2BRD_vg81VT=%2BhcM=P8-mSQLeNOKft0Q@mail.gmail.com> References: <Pine.NEB.4.64.1601072222060.9670@faeroes.freeshell.org> <CAOjFWZ5tGnNxQ5oYVW-%2BRD_vg81VT=%2BhcM=P8-mSQLeNOKft0Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 7 Jan 2016, Freddie Cash wrote: > When you create the pool on Solaris, pass along the version flag you want > to use (ZFSv28 is the last version in common with non-Solaris systems). > > When you create the pool on FreeBSD, pass along the version flag you want > to use (ZFSv28). I have read that the filesystem version is most important and that although both claim to support version 5, version 4 or earlier may be necessary on the Solaris sending side due to a send stream change for version 5 in Solaris after the fork. The filesystem version can be specified when it is created. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@freebsd.org Fri Jan 8 14:40:16 2016 Return-Path: <owner-freebsd-fs@freebsd.org> Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C53BEA682DE for <freebsd-fs@mailman.ysv.freebsd.org>; Fri, 8 Jan 2016 14:40:16 +0000 (UTC) (envelope-from kkeithle@redhat.com) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9E9751CDC for <freebsd-fs@freebsd.org>; Fri, 8 Jan 2016 14:40:16 +0000 (UTC) (envelope-from kkeithle@redhat.com) Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id 52065A35A5; Fri, 8 Jan 2016 14:40:16 +0000 (UTC) Received: from kkeithle.usersys.redhat.com (dhcp-41-176.bos.redhat.com [10.18.41.176]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u08EeFGu027047; Fri, 8 Jan 2016 09:40:15 -0500 Subject: Re: [Gluster-devel] FreeBSD port of GlusterFS racks up a lot of CPU usage To: Hubbard Jordan <jkh@ixsystems.com> References: <571237035.145690509.1451437960464.JavaMail.zimbra@uoguelph.ca> <20151230103152.GS13942@ndevos-x240.usersys.redhat.com> <2D8C2729-D556-479B-B4E2-66E1BB222F41@ixsystems.com> <568FC096.3080308@redhat.com> Cc: freebsd-fs <freebsd-fs@freebsd.org>, gluster-devel@gluster.org From: "Kaleb S. KEITHLEY" <kkeithle@redhat.com> Message-ID: <568FCA4F.2060804@redhat.com> Date: Fri, 8 Jan 2016 09:40:15 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <568FC096.3080308@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems <freebsd-fs.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>, <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>; List-Post: <mailto:freebsd-fs@freebsd.org> List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>, <mailto:freebsd-fs-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 08 Jan 2016 14:40:17 -0000 On 01/08/2016 08:58 AM, Kaleb S. KEITHLEY wrote: > On 12/30/2015 01:22 PM, Hubbard Jordan wrote: > >> I also have a broader question to go with the specific one: We >> (at iXsystems) were attempting to engage with some of the Red Hat >> folks back when the FreeBSD port was first done, in the hope of >> getting it more “officially supported” for FreeBSD and perhaps even >> donating some more serious stress-testing and integration work for >> it, but when those Red Hat folks moved on we lost continuity and >> the effort stalled. Who at Red Hat would / could we work with in >> getting this back on track? We’d like to integrate glusterfs with >> FreeNAS 10, and in fact have already done so but it’s still early >> days and we’re not even really sure what we have yet. >> > > Hi, > > To me, from a community standpoint, to be "officially supported" I'd > venture to say that what it takes is being visibly involved in the > project. That can take many forms, e.g., do regular builds on your > platform, submit bug reports (to our bugzilla) and associated fixes (to > our gerrit), implement and contribute new features, review other > people's patches in gerrit, build packages for your platform, evangelize > GlusterFS, answer questions in IRC and the mailing lists, etc., etc. > > Everything that goes on the community is done by volunteers. There are > no Red Hat employees whose sole responsibility is to work on Community > GlusterFS. (Excepting our Community Manager, Amye.) The Red Hat mantra > is "upstream first" so every feature and every bug fix that Red Hat > employees work on does indeed go into Community GlusterFS first; a lot > does get done as a side effect of that policy, but nobody should take it > for granted that _everything_ (or anything) will just get done. > > Nobody would say no to having serious stress testing and integration > work. If it plugs into our current gerrit and jenkins infrastructure, so > much the better. If there are people in your community who can help > maintain and/or grow our infrastructure, we could use a lot of help there. Just to be clear, by "our infrastructure" I mean Community GlusterFS infrastructure. > > With that level of involvement, I could imagine eventually FreeBSD > having more of a, I don't know, for lack of a better word, 'standing' in > the GlusterFS community. We do compile every patch on FreeBSD to ensure > that we don't break that level of portability, but that's the extent of > it. Maybe elevated to running regressions, as we do for NetBSD, which > has a bit of a legacy standing in the community due to Emmanuel Dreyfus' > long time participation. > > Anyway, that's my opinion. (Emphasis on my and opinion. Perhaps others > will weigh in with their opinions.) I look forward to your involvement > in the community. Look for us at FOSDEM, a couple of us will be there. > -- Kaleb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.2.01.1601080828550.28454>