From owner-freebsd-questions@FreeBSD.ORG Fri Jan 25 17:31:59 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EF1CFF01 for ; Fri, 25 Jan 2013 17:31:59 +0000 (UTC) (envelope-from bsd@todoo.biz) Received: from newmail.rmm.fr (newmail.rmm.fr [213.251.152.9]) by mx1.freebsd.org (Postfix) with ESMTP id B75BEB6A for ; Fri, 25 Jan 2013 17:31:59 +0000 (UTC) Received: from newmail.rmm.fr (newmail.rmm.fr [213.251.152.9]) by newmail.rmm.fr (Postfix) with ESMTP id 9C37F1477E0 for ; Fri, 25 Jan 2013 18:25:07 +0100 (CET) X-Virus-Scanned: amavisd-new 2.8.0 (20120630) at rmm.fr Received: from newmail.rmm.fr ([213.251.152.9]) by newmail.rmm.fr (newmail.rmm.fr [213.251.152.9]) (amavisd-new, port 10026) with ESMTP id PlehuYHri8J7 for ; Fri, 25 Jan 2013 18:25:07 +0100 (CET) Received: from newmail.rmm.fr (newmail.rmm.fr [87.98.206.99]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: hidden) by newmail.rmm.fr (Postfix) with ESMTPSA id 557FD1477D7 for ; Fri, 25 Jan 2013 18:25:07 +0100 (CET) From: bsd Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Best approach to jails + zfs Date: Fri, 25 Jan 2013 18:25:06 +0100 Message-Id: <6951EF94-E2BD-4B03-9F42-EA94BD23B718@todoo.biz> To: Liste FreeBSD Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2013 17:32:00 -0000 Hi,=20 I wanted to have the point of view of the community on the best approach = in order to handle a quite large system with couple of jails (shouldn't = have more than 5 to 10). Whole system is based on zfs. I'll use this as = a backup server. I have been using the "handbook" approach so far. It is quite stable but = the linked directories inside each jail is quite error prone and may be = confusing. With this approach you can update all your jails at once=85 = this is quite tempting, but if you have an error=85 all your jails are = gone at once ! =3D=3D you can't afford to have a kernel compile problem = while updating your system or you're dead !!=20 http://www.freebsd.org/doc//handbook/jails-build.html The other approach that I have found is to use create a base jail system = using sysinstall and then zfs snapshot to clone It. You then use this to = create a jail. You end up with couple of independent jails which are not = linked to each other in any way. You can / need to update each jail one = by one.=20 http://vocalbit.com/article/402/freebsd-jails-using-zfs-and-bsdinstall =95 I wanted to know if the handbook approach is still the most recent = one considering the latest progress in FBSD jail management ?=20 =95 I wanted to know if you had some "mixed" approach that can leverage = the risk of the handbook approach ?=20 =95 Last but not least - do you have any good pointer to recent guide / = howto / studies on the subject ?=20 Thanks=20 =96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96= =96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96 ---------> Gr=E9gory Bernard Director <--------- ---------------> www.osnet.eu <--------------- --> Your provider of OpenSource appliances <-- =96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96= =96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96=96 OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO