From owner-freebsd-amd64@freebsd.org  Wed Mar 23 12:00:06 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 E4ED0AD892C
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed, 23 Mar 2016 12:00:06 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 D5681117C
 for <freebsd-amd64@FreeBSD.org>; Wed, 23 Mar 2016 12:00:06 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u2NC06mq066279
 for <freebsd-amd64@FreeBSD.org>; Wed, 23 Mar 2016 12:00:06 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 206599] Geli restore from backuped geli-metadata is not possible
Date: Wed, 23 Mar 2016 12:00:06 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: marc.arnold.bach@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-geom@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-206599-6-ziqRRg6BmK@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-206599-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-206599-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 23 Mar 2016 12:27:55 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2016 12:00:07 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206599

--- Comment #2 from Bachmarc <marc.arnold.bach@gmail.com> ---
Yes and this I would regard as default because standing in an open door whi=
le
changing the lock is what people do... nobody would close the door to insta=
ll a
new  lock to get this thrill while not beeing sure if he will sees other si=
de
again.

Its a data block at the end of a device no on the fly transcrypting...


Even if not possible I would welcome a more meaningful error message: "Cann=
ot
perform action, cryptoprovider is still attached. Detach provider or set "f=
fot
shoot bit" ;o)"

--=20
You are receiving this mail because:
You are on the CC list for the bug.=