From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 11:32:03 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 284DF106564A; Wed, 9 Jul 2008 11:32:03 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id A3A358FC0A; Wed, 9 Jul 2008 11:32:02 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m69BW1aY064246; Wed, 9 Jul 2008 15:32:01 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Wed, 9 Jul 2008 15:32:01 +0400 (MSD) From: Dmitry Morozovsky To: Kris Kennaway In-Reply-To: <48749EA7.40702@FreeBSD.org> Message-ID: <20080709152739.Q58331@woozle.rinet.ru> References: <20080708100701.57031cda@twoflower.in.publishing.hu> <4873C4FA.2020004@FreeBSD.org> <20080709062533.J58331@woozle.rinet.ru> <48749087.4070802@FreeBSD.org> <20080709145010.Q58331@woozle.rinet.ru> <48749EA7.40702@FreeBSD.org> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Wed, 09 Jul 2008 15:32:01 +0400 (MSD) Cc: current@FreeBSD.org Subject: Re: Thinking of using ZFS/FBSD for a backup system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 09 Jul 2008 11:32:03 -0000 On Wed, 9 Jul 2008, Kris Kennaway wrote: KK> > marck@wizzle:/usr/ports> grep -Ril zfs Tools/ KK> > Tools/portbuild/scripts/claim-chroot KK> > Tools/portbuild/scripts/clean-chroot KK> > Tools/portbuild/scripts/cleanup-chroots KK> > KK> > ;-) KK> > KK> > Any pitfalls while using this? Thanks! KK> KK> It's still settling on pointyhat, but you could check it out there if you KK> like. The most annoying thing is actually a limitation of the FreeBSD NFS KK> server, since it returns errors to clients while it is reloading the export KK> list. Argh. And, which process is reporting an error? nfsd or some of kthreads? In the former case, is it possible to create new master-slave process tree, rebinding and signalling old tree to exit when all requests are finished? The same approach is used by www/nginx to both seamless configuration change and also binary file upgrade. CC:ing -current@ to ensure the theme have a bit broader audience. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------