From owner-freebsd-geom@FreeBSD.ORG Mon Feb 27 11:07:30 2012 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C53B71065673 for ; Mon, 27 Feb 2012 11:07:30 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A8B3F8FC13 for ; Mon, 27 Feb 2012 11:07:30 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1RB7U4D090196 for ; Mon, 27 Feb 2012 11:07:30 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1RB7Tx0090193 for freebsd-geom@FreeBSD.org; Mon, 27 Feb 2012 11:07:29 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 Feb 2012 11:07:29 GMT Message-Id: <201202271107.q1RB7Tx0090193@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org 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: Mon, 27 Feb 2012 11:07:30 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/165428 geom [glabel][patch] Add xfs support to glabel o kern/164254 geom [geom] gjournal not stopping on GPT partitions o kern/164252 geom [geom] gjournal overflow o kern/164143 geom [geom] Partition table not recognized after upgrade R8 a kern/163020 geom [geli] [patch] enable the Camellia-XTS on GEOM ELI o kern/162010 geom [geli] panic: Provider's error should be set (error=0) o kern/161979 geom [geom] glabel doesn't update after newfs, and glabel s o kern/161752 geom [geom] glabel(8) doesn't get gpt label change o bin/161677 geom gpart(8) Probably bug in gptboot o kern/160562 geom [geom][patch] Allow to insert new component to geom_ra o kern/160409 geom [geli] failed to attach provider f kern/159595 geom [geom] [panic] panic on gmirror unload in vbox [regres p kern/158398 geom [headers] [patch] includes o kern/158197 geom [geom] geom_cache with size>1000 leads to panics o kern/157879 geom [libgeom] [regression] ABI change without version bump o kern/157863 geom [geli] kbdmux prevents geli passwords from being enter o kern/157739 geom [geom] GPT labels with geom_multipath o kern/157724 geom [geom] gpart(8) 'add' command must preserve gap for sc o kern/157723 geom [geom] GEOM should not process 'c' (raw) partitions fo o kern/157108 geom [gjournal] dumpon(8) fails on gjournal providers o kern/155994 geom [geom] Long "Suspend time" when reading large files fr o kern/154226 geom [geom] GEOM label does not change when you modify them o kern/150858 geom [geom] [geom_label] [patch] glabel(8) is not compatibl o kern/150626 geom [geom] [gjournal] gjournal(8) destroys label o kern/150555 geom [geom] gjournal unusable on GPT partitions o kern/150334 geom [geom] [udf] [patch] geom label does not support UDF o kern/149762 geom volume labels with rogue characters o bin/149215 geom [panic] [geom_part] gpart(8): Delete linux's slice via o kern/147667 geom [gmirror] Booting with one component of a gmirror, the o kern/145818 geom [geom] geom_stat_open showing cached information for n o kern/145042 geom [geom] System stops booting after printing message "GE o kern/143455 geom gstripe(8) in RELENG_8 (31st Jan 2010) broken o kern/142563 geom [geom] [hang] ioctl freeze in zpool o kern/141740 geom [geom] gjournal(8): g_journal_destroy concurrent error o kern/140352 geom [geom] gjournal + glabel not working o kern/135898 geom [geom] Severe filesystem corruption - large files or l o kern/134922 geom [gmirror] [panic] kernel panic when use fdisk on disk o kern/134113 geom [geli] Problem setting secondary GELI key o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o bin/131415 geom [geli] keystrokes are unregulary sent to Geli when typ o kern/131353 geom [geom] gjournal(8) kernel lock o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid f kern/128276 geom [gmirror] machine lock up when gmirror module is used o kern/127420 geom [geom] [gjournal] [panic] Journal overflow on gmirrore o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/122738 geom [geom] gmirror list "losts consumers" after gmirror de o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120091 geom [geom] [geli] [gjournal] geli does not prompt for pass o kern/115856 geom [geli] ZFS thought it was degraded when it should have o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/114532 geom [geom] GEOM_MIRROR shows up in kldstat even if compile f kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o bin/86388 geom [geom] [geom_part] periodic(8) daily should backup gpa o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. 71 problems total. From owner-freebsd-geom@FreeBSD.ORG Wed Feb 29 04:13:25 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 96DCB106566B; Wed, 29 Feb 2012 04:13:25 +0000 (UTC) (envelope-from jwd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 836598FC1E; Wed, 29 Feb 2012 04:13:25 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1T4DP0p030359; Wed, 29 Feb 2012 04:13:25 GMT (envelope-from jwd@freefall.freebsd.org) Received: (from jwd@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1T4DPgD030358; Wed, 29 Feb 2012 04:13:25 GMT (envelope-from jwd) Date: Wed, 29 Feb 2012 04:13:25 +0000 From: John To: freebsd-fs@freebsd.org, freebsd-geom@freebsd.org Message-ID: <20120229041325.GA4447@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: GEOM tasting iscsi zvols? 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: Wed, 29 Feb 2012 04:13:25 -0000 Hi Folks, I noticed (actually looked at my serial console logs :) that GEOM appears to be tasting the zvols being exported via iscsi(istgt). For instance: multipath completes... GEOM_MULTIPATH: da405 added to Z22 GEOM_MULTIPATH: da406 added to Z23 GEOM_MULTIPATH: da407 added to Z24 load zfs... ZFS filesystem version 5 ZFS storage pool version 28 luns tasted... GEOM_PART: integrity check failed (zvol/pool0/d00000003_300g_16k, MBR) GEOM_PART: integrity check failed (zvol/pool0/d00000003_300g_16k@snap1, MBR) GEOM_PART: integrity check failed (zvol/pool0/d00000001_300g_16k, MBR) GEOM_PART: integrity check failed (zvol/pool0/d00000001_300g_16k@snap1, MBR) The zvols have never been accessed/formatted from the local system except via the istgt daemon from the client. Is there a way to disable this that I've somehow missed? man 4 GEOM mentions "tasting" and the logic around this operation. A google search shows a couple of similar questions - no discrete answers. Comments welcome. Thanks, John From owner-freebsd-geom@FreeBSD.ORG Wed Feb 29 14:59:27 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 57263106566C for ; Wed, 29 Feb 2012 14:59:27 +0000 (UTC) (envelope-from feld@feld.me) Received: from mwi1.coffeenet.org (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 204518FC22 for ; Wed, 29 Feb 2012 14:59:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:To:Content-Type; bh=Trof4OJDzSnisDj9WdaenTOu57cEbCLcZ9RNq3BzECs=; b=LekNFpc4TXJ6lfLE/bJhV8euMJR6YoI3jRGkC2OstDlJE1XczafiW+IC/Xm36kFB9AURzEFBKP/3jjtfP6SWCJJ2Ruh0gmFZJ0u4NJx45pIyvLhP97KOEyjzvLO0XqLF; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by mwi1.coffeenet.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1S2kzx-0008Bz-Mq for freebsd-geom@freebsd.org; Wed, 29 Feb 2012 08:59:26 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1330527555-13047-13046/5/31; Wed, 29 Feb 2012 14:59:15 +0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-geom@freebsd.org References: <20120229041325.GA4447@FreeBSD.org> Date: Wed, 29 Feb 2012 08:59:15 -0600 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: <20120229041325.GA4447@FreeBSD.org> User-Agent: Opera Mail/11.62 (FreeBSD) X-SA-Score: -1.5 Subject: Re: GEOM tasting iscsi zvols? 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: Wed, 29 Feb 2012 14:59:27 -0000 On Tue, 28 Feb 2012 22:13:25 -0600, John wrote: > > Is there a way to disable this that I've somehow missed? man 4 GEOM > mentions "tasting" and the logic around this operation. A google search > shows a couple of similar questions - no discrete answers. It does this for me as well -- 16 iSCSI luns get "tested" every time you restart istgt. It doesn't cause an issue here, though. Do you experience any problems? It really shouldn't cause any issues to have the GEOM layer peek into those zvols to see if there is anything it can use. From owner-freebsd-geom@FreeBSD.ORG Wed Feb 29 15:23:09 2012 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67EC91065675 for ; Wed, 29 Feb 2012 15:23:09 +0000 (UTC) (envelope-from feld@feld.me) Received: from mwi1.coffeenet.org (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3E8838FC15 for ; Wed, 29 Feb 2012 15:23:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:To:Content-Type; bh=5HAIvedctsZohlf34ehwy3ldngWyDwGHcujkPMnvrQA=; b=Dx4nLBTwzCrqj1n6PJ+d5P7zPXRZ5KkQ1fI34W7nkJdKSrRgKHgcef0YjA5NtZgxC0h5BLePilE/DeLMySGy/YrpoIesWhhgJkLCYf6j9Wy7Mdx1M/HMUG4ojBvgoXc4; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by mwi1.coffeenet.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1S2lMx-0008q8-HT for freebsd-geom@freebsd.org; Wed, 29 Feb 2012 09:23:08 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1330528981-13047-13046/5/32; Wed, 29 Feb 2012 15:23:01 +0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-geom@freebsd.org References: <20120229041325.GA4447@FreeBSD.org> Date: Wed, 29 Feb 2012 09:23:01 -0600 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: User-Agent: Opera Mail/11.62 (FreeBSD) X-SA-Score: -1.5 Subject: Re: GEOM tasting iscsi zvols? 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: Wed, 29 Feb 2012 15:23:09 -0000 On Wed, 29 Feb 2012 08:59:15 -0600, Mark Felder wrote: > 16 iSCSI luns get "tested" Whoops, I meant "tasted" From owner-freebsd-geom@FreeBSD.ORG Fri Mar 2 03:25:26 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 72317106564A for ; Fri, 2 Mar 2012 03:25:26 +0000 (UTC) (envelope-from rsimmons0@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id E836E8FC14 for ; Fri, 2 Mar 2012 03:25:25 +0000 (UTC) Received: by lagv3 with SMTP id v3so2127062lag.13 for ; Thu, 01 Mar 2012 19:25:24 -0800 (PST) Received-SPF: pass (google.com: domain of rsimmons0@gmail.com designates 10.112.100.169 as permitted sender) client-ip=10.112.100.169; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rsimmons0@gmail.com designates 10.112.100.169 as permitted sender) smtp.mail=rsimmons0@gmail.com; dkim=pass header.i=rsimmons0@gmail.com Received: from mr.google.com ([10.112.100.169]) by 10.112.100.169 with SMTP id ez9mr3354710lbb.82.1330658724957 (num_hops = 1); Thu, 01 Mar 2012 19:25:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=JeT4/nURO19fmVsqXTXjlIdMtlvPEfs0nxl9LBcO6JA=; b=Pr+G4nnbCekh55TeOjfeZB1Qx5A+x/L7u2TXRptLLKI+aKv6H+pPhhdFil7/0AZKr1 yq61+4RWI/tN9M6KyysXI/awYC/lKRyrolwLltnB132NuUVLYnnC36A9Pp2TXCmfJwPv vYfgmxONq1VwxoUti+ciw3XDVFWiAy4Xk7V10q8Dd6g2ElQNpMZ6B4ty871t6qYwLKR0 T7pZyLrYYHBeen91C1TkS1YXjsrVfUGPUWerZiL0F6RcNjdvenaQU8syrVZ2rM2lAcU0 M+TmDHBXgN/PQZJfGa/rtCAb7/q0m53uLKJ+8mkv9FRvzYwn/XIIPZBejrl4WiznpEPu eSLQ== MIME-Version: 1.0 Received: by 10.112.100.169 with SMTP id ez9mr2718059lbb.82.1330657217300; Thu, 01 Mar 2012 19:00:17 -0800 (PST) Received: by 10.112.145.73 with HTTP; Thu, 1 Mar 2012 19:00:17 -0800 (PST) Date: Thu, 1 Mar 2012 22:00:17 -0500 Message-ID: From: Robert Simmons To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: 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 03:25:26 -0000 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. and lots more errors exactly like this. These are produced because the checksums have not been initialized yet. In the manpage of geli it states "It is recommended to write the whole provider before the first use, in order to make sure that all sectors and their corresponding checksums are properly initialized into a consistent state." These errors are no problem at all, but they look scary when you first encounter them and you don't realize why they are being produced. 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. An alternative is to 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. Thoughts? 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 From owner-freebsd-geom@FreeBSD.ORG Sat Mar 3 22:24:16 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 1AA24106564A for ; Sat, 3 Mar 2012 22:24:16 +0000 (UTC) (envelope-from rsimmons0@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id C0E0B8FC16 for ; Sat, 3 Mar 2012 22:24:15 +0000 (UTC) Received: by vcmm1 with SMTP id m1so1408517vcm.13 for ; Sat, 03 Mar 2012 14:24:15 -0800 (PST) Received-SPF: pass (google.com: domain of rsimmons0@gmail.com designates 10.52.92.140 as permitted sender) client-ip=10.52.92.140; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rsimmons0@gmail.com designates 10.52.92.140 as permitted sender) smtp.mail=rsimmons0@gmail.com; dkim=pass header.i=rsimmons0@gmail.com Received: from mr.google.com ([10.52.92.140]) by 10.52.92.140 with SMTP id cm12mr25557817vdb.115.1330813455149 (num_hops = 1); Sat, 03 Mar 2012 14:24:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=1ODgncwu7ffpQ70QDoJZrOH96m9yqAtZRk7a4lwa/2A=; b=VMiVrrExJdab8mYWYRDPtQ19nTVgqBA2heqnxEFS/4sj2mqLq8d7ngzFkklXoqcSpZ CQCUfd0pN2qm4ZSqqYA5lc0mKGrRmnK5tX3h/iCHIaNm72dUm3MkZewv6n32kpDIA5wI Af4qeujMqsfObc3x2ek+dK3vgbG0Ty1f0lGTPeuBAEtSD0SNBOyUgYRUh6ijmX/LZx7Z YIFHlmTM5CmSpBcaPZXoH84P1asWPu2AsR2h/nsKEmcN3914toNWiI43GhYDC9VQDnyf Pdi9Zbq+IMvYgmiCM0SU92D6ZF0844WgEpUHgUcvjAddBeT6niNNgV5OW1EFE6HdxGny Th6A== MIME-Version: 1.0 Received: by 10.52.92.140 with SMTP id cm12mr21886930vdb.115.1330813455105; Sat, 03 Mar 2012 14:24:15 -0800 (PST) Received: by 10.52.65.114 with HTTP; Sat, 3 Mar 2012 14:24:15 -0800 (PST) Date: Sat, 3 Mar 2012 17:24:15 -0500 Message-ID: From: Robert Simmons To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: geli metadata backup 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: Sat, 03 Mar 2012 22:24:16 -0000 What exactly is contained in the metadata backup file /var/backups/_prov_.eli ? Obviously, since I keep /var inside of the encrypted provider, the default location is a bad place for a backup. Where would a good location be to save this metadata using the -B switch for geli init other than the default? I have /home /root /tmp /usr and /var inside the encrypted provider. Everything else is unencrypted.