From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 20:00:03 2013 Return-Path: Delivered-To: freebsd-current@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 ESMTP id E9D8B432 for ; Thu, 10 Oct 2013 20:00:03 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A098F2877 for ; Thu, 10 Oct 2013 20:00:03 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1VUMOp-000jQV-6h>; Thu, 10 Oct 2013 21:59:55 +0200 Received: from g226176073.adsl.alicedsl.de ([92.226.176.73] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1VUMOp-000ADP-0s>; Thu, 10 Oct 2013 21:59:55 +0200 Date: Thu, 10 Oct 2013 21:59:49 +0200 From: "O. Hartmann" To: freebsd-current@freebsd.org Subject: Re: FreeBSD 10 and zfsd Message-ID: <20131010215949.3214f4c2@thor.walstatt.dyndns.org> In-Reply-To: <1381430466.14387.32509497.13949CED@webmail.messagingengine.com> References: <5256B761.4050301@gmail.com> <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> <5256E2D5.4060101@allanjude.com> <5256E680.4000008@allanjude.com> <1381430466.14387.32509497.13949CED@webmail.messagingengine.com> Organization: FU Berlin X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/N1_XIULFj4LrssVhhs2rUzG"; protocol="application/pgp-signature" X-Originating-IP: 92.226.176.73 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 20:00:04 -0000 --Sig_/N1_XIULFj4LrssVhhs2rUzG Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 10 Oct 2013 13:41:06 -0500 Mark Felder wrote: >=20 >=20 > On Thu, Oct 10, 2013, at 12:40, Allan Jude wrote: > > On 2013-10-10 13:26, Alan Somers wrote: > > > On Thu, Oct 10, 2013 at 11:24 AM, Allan Jude > > > wrote: > > >> On 2013-10-10 12:13, Mark Felder wrote: > > >>> On Thu, Oct 10, 2013, at 10:24, Alan Somers wrote: > > >>>> On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks > > >>>> wrote: > > >>>>> When i started using ZFS on FreeBSD I quickly found out that > > >>>>> hot spares are not possible on FreeBSD. > > >>>>> I was told that with zfsd it should be possible and that it > > >>>>> would be included in FreeBSD 10. > > >>>>> > > >>>>> Is there some info about the zfsd function and how it could > > >>>>> be used? > > >>>> zfsd is currently not in FreeBSD/head and won't make it into > > >>>> 10, but you can still get the source code from its project > > >>>> branch. It's being used in production by at least two > > >>>> companies. > > >>>> > > >>> So FreeBSD is going to have inferior ZFS management compared to > > >>> Solaris/Illumos/etc for another 2+ years? Why are things like > > >>> this allowed to miss releases? > > >>> _______________________________________________ > > >>> freebsd-current@freebsd.org mailing list > > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > > >>> To unsubscribe, send any mail to > > >>> "freebsd-current-unsubscribe@freebsd.org" > > >> ZFSd was a big topic of discussion at the EuroBSDCon 2013 dev > > >> summit (3 weeks ago). There is a lot of collaboration going on, > > >> to bring in some work done by vendors like SpectraLogics. This > > >> is the type of feature that can be assed in 10.1, it won't have > > >> to wait for 11. > > >> > > >> You can see Robert Watsons talk "How FreeBSD Works" to see why > > >> releases are based on date, rather than on feature completion > > >> (because things are never "finished") > > >> > > >> > > >> > > >> -- > > >> Allan Jude > > >> > > >> _______________________________________________ > > >> freebsd-current@freebsd.org mailing list > > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > > >> To unsubscribe, send any mail to > > >> "freebsd-current-unsubscribe@freebsd.org" > > > Due to popular demand, I have located a round toit. I'm currently > > > working on rebasing the zfsd project branch to head, after which > > > I'll push SpectraLogic's recent changes. > > See, all you have to do is complain loudly enough :p > >=20 >=20 > I was sad more than anything. I'd been waiting for zfsd since the > project was announced. :-) I'm glad to know we won't have to wait > until 11.0. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" Ha! Very funny. I created a RAIDZ1 pool and by reading the man page for zpool, which states precisely how to create a hot spare for a given pool. I wasn't aware until now that this action was useless, and even dangerous. Well, bravo, I must admit, the man page does not give any kind of warning that one can not rely on a hot spare. oh --Sig_/N1_XIULFj4LrssVhhs2rUzG Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQEcBAEBAgAGBQJSVwc5AAoJEOgBcD7A/5N85bQIAMfeBgJikS2PhK0m+/zU4wLa Xtlnv/YTPl+bJ4UssgF4J6G/dorHD6nKocc1hJzAmohkBPkqgdP4nx+r2sOYGJuA kPNJvcAmHaCAnPZgMhUYLMSCi/MVDVDOD7KzMTtkVyOeM/BPXyXxAR7wqGbvXlU+ +UkLca3feYQ/O2gozbdTfaBmfBnUCITleVMGQV4dxTTce0rh3ZZKVHW5iIoD9XeX 5og1/XC6C/ZDLi9sIQuruDdjEduKAQq4K/t9WPHz4/btZ1ZBBsRkQfExswcK3kWL hQMYfK1V4suPlbz1yRcZeOhyNZAK4xxSrhEC3my60GnZsVndk4TOGyHy7L2CIUU= =dC9b -----END PGP SIGNATURE----- --Sig_/N1_XIULFj4LrssVhhs2rUzG--