From owner-freebsd-geom@FreeBSD.ORG Fri Mar 2 13:44:21 2012 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6A9D0106566B for ; Fri, 2 Mar 2012 13:44:21 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id E3E618FC0A for ; Fri, 2 Mar 2012 13:44:20 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so804855wib.13 for ; Fri, 02 Mar 2012 05:44:19 -0800 (PST) Received-SPF: pass (google.com: domain of rwmaillists@googlemail.com designates 10.216.131.210 as permitted sender) client-ip=10.216.131.210; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rwmaillists@googlemail.com designates 10.216.131.210 as permitted sender) smtp.mail=rwmaillists@googlemail.com; dkim=pass header.i=rwmaillists@googlemail.com Received: from mr.google.com ([10.216.131.210]) by 10.216.131.210 with SMTP id m60mr1347584wei.47.1330695859965 (num_hops = 1); Fri, 02 Mar 2012 05:44:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=fJr3nLbbbKDk7S4VqFukn2W1CVOGcWrKwmn0be8v02Y=; b=QmC+YADgqgN4Wz5c45AdXgqake4Xcv8QoJWM1OzHT5/6bJv8b0iqQwaA/Dir5r982K BldC/fk746CnPkpMycVq4Pu8kdWL+NQokoex9jX4f6QmAiFoUjVu749hm6P7fvuRD4RH /0RoPquB72CFT/C5LHiihcaAScKx01U7eadGsyYg3AHdyhUV493dV6JhoI1fZWzeDz+D 4vCGl6sywoTFoIKnKcSUNU77x2g/cetNJKFGaIhdQQSDTov9YEwKtzEoBFYjCpcHnK+C gFRcUjS3emE3Pd0aPSf9aaAwDLmedf4UxdsNOcmwtboOs8SAtHMH6c3DeilFlce7OA0a qBZw== Received: by 10.216.131.210 with SMTP id m60mr1021648wei.47.1330694073905; Fri, 02 Mar 2012 05:14:33 -0800 (PST) Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk. [87.194.105.247]) by mx.google.com with ESMTPS id cc3sm9757633wib.7.2012.03.02.05.14.31 (version=SSLv3 cipher=OTHER); Fri, 02 Mar 2012 05:14:32 -0800 (PST) Date: Fri, 2 Mar 2012 13:14:29 +0000 From: RW To: freebsd-geom@freebsd.org Message-ID: <20120302131429.183b491d@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: geli init for first time X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2012 13:44:21 -0000 On Thu, 1 Mar 2012 22:00:17 -0500 Robert Simmons wrote: > After you perform "geli init" and "geli attach" you must use dd to > initialize the new provider before you run newfs. If you had enabled > authentication of some kind during the init step, when you attach the > provider you get a series of errors such as these: > GEOM_ELI: ada0p4.eli: 4096 bytes corrupted at offset 0. > GEOM_ELI: ada0p4.eli: 4096 bytes corrupted at offset 4096. > > ... > I propose that a switch be added to "geli attach" that signifies that > it is the first time that a provider is being attached and these > errors are to be suppressed. If you know to use the switch then you'd know that the warnings are harmless. Perhaps it would be better to make the warning more accurate: GEOM_ELI: ada0p4.eli: 4096 bytes not authenticated at offset 4096. > ... add something to the end of the DATA > AUTHENTICATION section of the geli(8) man page that mentions why these > errors occur and that they can be safely ignored. Good idea