From owner-freebsd-questions@freebsd.org Wed Apr 26 16:05:49 2017 Return-Path: Delivered-To: freebsd-questions@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 1F8DED51BF2 for ; Wed, 26 Apr 2017 16:05:49 +0000 (UTC) (envelope-from asv@inhio.net) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DE2D4E69 for ; Wed, 26 Apr 2017 16:05:47 +0000 (UTC) (envelope-from asv@inhio.net) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 6E48E60F2E for ; Wed, 26 Apr 2017 12:05:45 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CoIynYoXWj4P for ; Wed, 26 Apr 2017 12:05:44 -0400 (EDT) Received: from inet07.hamilton.harte-lyne.ca (inet07.hamilton.harte-lyne.ca [216.185.71.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "imap.hamilton.harte-lyne.ca", Issuer "CA HLL ISSUER 01" (not verified)) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPS for ; Wed, 26 Apr 2017 12:05:44 -0400 (EDT) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (verified OK)) by inet07.hamilton.harte-lyne.ca (Postfix) with ESMTPS id F3DD38A534; Wed, 26 Apr 2017 12:05:43 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id D614860F2E; Wed, 26 Apr 2017 12:05:43 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aHVi7do0warA; Wed, 26 Apr 2017 12:05:42 -0400 (EDT) X-Greylist: delayed 367 seconds by postgrey-1.34 at inet08.hamilton.harte-lyne.ca; Wed, 26 Apr 2017 12:05:41 EDT Received: from cz-prg-mx-01.inhio.eu (mail.inhio.eu [178.238.36.226]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP; Wed, 26 Apr 2017 12:05:41 -0400 (EDT) Received: from [192.168.0.9] (unknown [179.210.96.127]) by cz-prg-mx-01.inhio.eu (Postfix) with ESMTPSA id 252C92D76C; Wed, 26 Apr 2017 15:59:28 +0000 (UTC) Message-ID: <1493222366.2938.10.camel@inhio.net> Subject: Re: Undo GELI From: ASV To: byrnejb@harte-lyne.ca, freebsd-questions@harte-lyne.ca Date: Wed, 26 Apr 2017 12:59:26 -0300 In-Reply-To: <74584efb8720147d119d31fcb452a521.squirrel@webmail.harte-lyne.ca> References: <74584efb8720147d119d31fcb452a521.squirrel@webmail.harte-lyne.ca> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2017 16:05:49 -0000 Unfortunately for you the geli provider must be created prior the filesystem which is going to be encrypted within. If you forgot about that you have to move the data somewhere else and re-create the fs within a geli provider. As I've played quite some with that in the past I can tell you that I've successfully used rsync, dump and tar for the data transfer. Which one to use is up to you but dump is certainly the slowest of them all. Good luck! On Tue, 2017-04-25 at 13:01 -0400, James B. Byrne via freebsd-questions wrote: > In my frustration with getting FreeBSD installed on it I forgot where > this device was going to be placed and selected encryption for the > entire ZFS install.  I now realise that simply is not going to work.  > Having already extensively configured the unit I am wondering if > there > is some way to undo this or if I am faced with a complete reinstall. > > Sigh. . . > >