From owner-freebsd-geom@FreeBSD.ORG  Tue Sep 21 07:08:40 2004
Return-Path: <owner-freebsd-geom@FreeBSD.ORG>
Delivered-To: freebsd-geom@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 885EC16A4CE
	for <freebsd-geom@freebsd.org>; Tue, 21 Sep 2004 07:08:40 +0000 (GMT)
Received: from fmmailgate03.web.de (fmmailgate03.web.de [217.72.192.234])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E46C343D46
	for <freebsd-geom@freebsd.org>; Tue, 21 Sep 2004 07:08:39 +0000 (GMT)
	(envelope-from ilsa.gold@web.de)
Received: by fmmailgate03.web.de (8.12.6/8.12.6/webde Linux 0.7) with SMTP id
	i8L77e04014015
	for freebsd-geom@freebsd.org; Tue, 21 Sep 2004 09:08:38 +0200
Received: from 62.180.31.25 by freemailng0106.web.de with HTTP;
	Tue, 21 Sep 2004 09:08:37 +0200
Date: Tue, 21 Sep 2004 09:08:37 +0200
Message-Id: <1293070566@web.de>
MIME-Version: 1.0
From: =?iso-8859-1?Q? "Stefan=20Krau=DF" ?= <ilsa.gold@web.de>
To: freebsd-geom@freebsd.org
Precedence: fm-user
Organization: http://freemail.web.de/
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Another problem with not re-attachable gbde slice
X-BeenThere: freebsd-geom@freebsd.org
X-Mailman-Version: 2.1.1
List-Id: GEOM-specific discussions and implementations
	<freebsd-geom.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-geom>
List-Post: <mailto:freebsd-geom@freebsd.org>
List-Help: <mailto:freebsd-geom-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2004 07:08:40 -0000

Hello list,

I wrote a few weeks ago about a problem with reattaching a gbde encrypted slice under FreeBSD 5.2.1. The slice worked for about 3 month without any problem (could be attached, detached and so on). After writing lots of data to this attached slice (about 9-10 Gig) the slice couldn't be attached any more. There appeared no /dev/ad0s3a.bde-device file after an "gbde attach /dev/ad0s3a -l /etc/gbde/ad0s3a".

I upgraded to RELENG_5 last sunday hoping that this maybe solve my problem, but it didn't. So I tried the follwing command to change my key (just to check if the access to my key is borken) and got an error:

# gbde setkey /dev/ad0s3a -l /etc/gbde/ad0s3a
Enter passphrase: <I entered the 100% correct passphrase here>
gbde: Lock not found

Did I something wrong or is the gbde-slice finally unusable (I read a few maillings in this list that there were some bugs regarding the reattaching of gbde-slices)?


Best regards
Stefan
_______________________________________________________
WEB.DE Video-Mail - Sagen Sie mehr mit bewegten Bildern
Informationen unter: http://freemail.web.de/?mc=021199