From owner-freebsd-geom@FreeBSD.ORG Tue Sep 21 12:45:43 2004 Return-Path: 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 188CF16A4CE for ; Tue, 21 Sep 2004 12:45:43 +0000 (GMT) Received: from afields.ca (afields.ca [216.194.67.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF31343D31 for ; Tue, 21 Sep 2004 12:45:42 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (localhost.afields.ca [127.0.0.1]) by afields.ca (8.12.11/8.12.11) with ESMTP id i8LCjgDO064781; Tue, 21 Sep 2004 08:45:42 -0400 (EDT) (envelope-from afields@afields.ca) Received: (from afields@localhost) by afields.ca (8.12.11/8.12.11/Submit) id i8LCjg9V064780; Tue, 21 Sep 2004 08:45:42 -0400 (EDT) (envelope-from afields) Date: Tue, 21 Sep 2004 08:45:42 -0400 From: Allan Fields To: =?us-ascii?B?PT9pc28tODg1OS0xP1E/?= Stefan=20Krau=DF ?= Message-ID: <20040921124542.GE47410@afields.ca> References: <1293070566@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1293070566@web.de> User-Agent: Mutt/1.4i cc: freebsd-geom@freebsd.org Subject: Re: Another problem with not re-attachable gbde slice X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 12:45:43 -0000 On Tue, Sep 21, 2004 at 09:08:37AM +0200, =?iso-8859-1?Q? Stefan=20Krau=DF ?= wrote: > 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 observed similar and was able to reproduce this behaviour as you/others have encountered with a test volume: usually it took a while to fill up the filesystem enough. > 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: > gbde: Lock not found That is because it would attempt to find a now non-existent and likely moved-in-location lock sector. > 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)? Afraid not. I take it your existing device couldn't be reattached with the newest patch applied: This isn't unexpected given the most likely cause of your problem was that the lock sector had been overwritten, if you only had one key, then that option has been exhausted. > Best regards > Stefan Thanks for your and others' reports.. -- Allan Fields, AFRSL - http://afields.ca 2D4F 6806 D307 0889 6125 C31D F745 0D72 39B4 5541