From owner-freebsd-geom@FreeBSD.ORG Mon Feb 28 11:06:59 2011 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 0B5671065672 for ; Mon, 28 Feb 2011 11:06:59 +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 ED3A78FC1A for ; Mon, 28 Feb 2011 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1SB6wSq011970 for ; Mon, 28 Feb 2011 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1SB6wCw011968 for freebsd-geom@FreeBSD.org; Mon, 28 Feb 2011 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 Feb 2011 11:06:58 GMT Message-Id: <201102281106.p1SB6wCw011968@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, 28 Feb 2011 11:06:59 -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/154226 geom [geom] GEOM label does not change when you modify them o kern/152609 geom [geli] geli onetime on gzero panics 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/144905 geom [geom][geom_part] panic in gpart_ctlreq when unpluggin 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 kern/132273 geom glabel(8): [patch] failing on journaled partition 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/88601 geom [geli] geli cause kernel panic under heavy disk usage 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. 53 problems total. From owner-freebsd-geom@FreeBSD.ORG Wed Mar 2 07:37:33 2011 Return-Path: Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3B9B1065670; Wed, 2 Mar 2011 07:37:33 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 79BD18FC18; Wed, 2 Mar 2011 07:37:33 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p227bXo7034259; Wed, 2 Mar 2011 07:37:33 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p227bXg2034255; Wed, 2 Mar 2011 07:37:33 GMT (envelope-from linimon) Date: Wed, 2 Mar 2011 07:37:33 GMT Message-Id: <201103020737.p227bXg2034255@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-geom@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/155118: [geom] geom_eli containers created on systems with aesni(4) enabled are not working on systems without aesni(4) and vice versa. 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, 02 Mar 2011 07:37:33 -0000 Old Synopsis: geom_eli containers created on systems with aesni(4) enabled are not working on systems without aesni(4) and vice versa. New Synopsis: [geom] geom_eli containers created on systems with aesni(4) enabled are not working on systems without aesni(4) and vice versa. Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Wed Mar 2 07:37:13 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=155118 From owner-freebsd-geom@FreeBSD.ORG Wed Mar 2 14:44:56 2011 Return-Path: Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1323C1065672; Wed, 2 Mar 2011 14:44:56 +0000 (UTC) (envelope-from kib@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DD6BB8FC2D; Wed, 2 Mar 2011 14:44:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p22Eit5Q055372; Wed, 2 Mar 2011 14:44:55 GMT (envelope-from kib@freefall.freebsd.org) Received: (from kib@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p22Eitjn055368; Wed, 2 Mar 2011 14:44:55 GMT (envelope-from kib) Date: Wed, 2 Mar 2011 14:44:55 GMT Message-Id: <201103021444.p22Eitjn055368@freefall.freebsd.org> To: kib@FreeBSD.org, freebsd-geom@FreeBSD.org, kib@FreeBSD.org From: kib@FreeBSD.org Cc: Subject: Re: kern/155118: [aesni] geom_eli containers created on systems with aesni(4) enabled are not working on systems without aesni(4) and vice versa. 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, 02 Mar 2011 14:44:56 -0000 Old Synopsis: [geom] geom_eli containers created on systems with aesni(4) enabled are not working on systems without aesni(4) and vice versa. New Synopsis: [aesni] geom_eli containers created on systems with aesni(4) enabled are not working on systems without aesni(4) and vice versa. Responsible-Changed-From-To: freebsd-geom->kib Responsible-Changed-By: kib Responsible-Changed-When: Wed Mar 2 14:44:18 UTC 2011 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=155118 From owner-freebsd-geom@FreeBSD.ORG Thu Mar 3 14:47:47 2011 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 255C31065670 for ; Thu, 3 Mar 2011 14:47:47 +0000 (UTC) (envelope-from xi@borderworlds.dk) Received: from kazon.borderworlds.dk (kazon.borderworlds.dk [IPv6:2a01:4f8:101:4201::1:1]) by mx1.freebsd.org (Postfix) with ESMTP id B4FE38FC14 for ; Thu, 3 Mar 2011 14:47:46 +0000 (UTC) Received: from borg.borderworlds.dk (localhost [127.0.0.1]) by kazon.borderworlds.dk (Postfix) with ESMTP id 665725C3B for ; Thu, 3 Mar 2011 15:47:45 +0100 (CET) Message-ID: <4D6FAA10.5040202@borderworlds.dk> Date: Thu, 03 Mar 2011 15:47:44 +0100 From: Christian Laursen Organization: The Border Worlds User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.14) Gecko/20110302 Thunderbird/3.1.8 MIME-Version: 1.0 To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Is it possible to delay the root mount? 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: Thu, 03 Mar 2011 14:47:47 -0000 Hello, I'm having some problems when booting from a USB memstick and mounting root from a /dev/label partition on said memstick. I am using 8.2-RELEASE. I get the usual "Root mount waiting for: usbXX" message when booting but most of the time when the kernel is done waiting the /dev/label partition has not yet been detected and the root mount then fails. It seems to depend on the timing of the USB discovery. I plugged in a USB keyboard to be able to enter the correct device at the mountroot prompt and that changed the timing in a way that made the root mount succeed... Is there a way to make the root mount wait for a specific device like /dev/label/myroot? Even a statically configured sleep before mounting root would solve my problem. If there is an easy way to patch such a thing into the kernel I would be happy. A tunable would of course be event better. Thanks in advance for any help regarding this. By the way, the box I'm working with is documented a little bit here: http://borderworlds.dk/~xi/BRIK/ -- Christian Laursen From owner-freebsd-geom@FreeBSD.ORG Thu Mar 3 17:52:16 2011 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 DB2691065672 for ; Thu, 3 Mar 2011 17:52:16 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: from paka.cyberleo.net (paka.cyberleo.net [66.219.31.21]) by mx1.freebsd.org (Postfix) with ESMTP id B643C8FC13 for ; Thu, 3 Mar 2011 17:52:16 +0000 (UTC) Received: from [172.16.44.4] (den.cyberleo.net [66.253.36.39]) by paka.cyberleo.net (Postfix) with ESMTPSA id 1998929652; Thu, 3 Mar 2011 12:35:56 -0500 (EST) Message-ID: <4D6FD17B.2040800@cyberleo.net> Date: Thu, 03 Mar 2011 11:35:55 -0600 From: CyberLeo Kitsana User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101218 Lightning/1.0b3pre Thunderbird/3.1.7 MIME-Version: 1.0 To: Christian Laursen References: <4D6FAA10.5040202@borderworlds.dk> In-Reply-To: <4D6FAA10.5040202@borderworlds.dk> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org Subject: Re: Is it possible to delay the root mount? 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: Thu, 03 Mar 2011 17:52:16 -0000 On 03/03/2011 08:47 AM, Christian Laursen wrote: > Is there a way to make the root mount wait for a specific device like > /dev/label/myroot? Set kern.cam.scsi_delay in milliseconds in loader.conf. I have it set to 5000 to boot from a particularly lazy USB flash drive. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://wwww.fur.com/peace/ From owner-freebsd-geom@FreeBSD.ORG Sat Mar 5 22:20:46 2011 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 1A4A2106564A for ; Sat, 5 Mar 2011 22:20:46 +0000 (UTC) (envelope-from terje@elde.net) Received: from keepquiet.net (keepquiet.net [IPv6:2a01:4f8:130:84c1::deaf:babe]) by mx1.freebsd.org (Postfix) with ESMTP id D1F988FC08 for ; Sat, 5 Mar 2011 22:20:45 +0000 (UTC) Received: from [10.130.10.194] (cm-84.209.214.220.getinternet.no [84.209.214.220]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: terje@elde.net) by keepquiet.net (Postfix) with ESMTPSA id C4CCE2E128 for ; Sat, 5 Mar 2011 23:20:44 +0100 (CET) From: Terje Elde Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sat, 5 Mar 2011 23:20:43 +0100 Message-Id: To: freebsd-geom@freebsd.org Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) Subject: Using both GELI and labels on bootdevices 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, 05 Mar 2011 22:20:46 -0000 Hi, I'd like to use both GELI and GPT labels on boot devices. There are two = reasons for this: a) The usual benefits of labels, being able jump between AHCI and other = drivers, being able to toss a drive in an enclose and use it just the = same, etc, and b) I find it comfortable to match the name of keyfiles to labels, = rather than (possibly temporary) devicenames or something else. Normal way of loading keyfiles at boot would be: geli_da0_keyfile0_load=3D"YES" geli_da0_keyfile0_type=3D"da0:geli_keyfile0" geli_da0_keyfile0_name=3D"/boot/keys/da0.key0" I haven't tested, but suspect this wouldn't work: geli_gpt/foo_keyfile0_load=3D"YES" geli_gpt/foo_keyfile0_type=3D"gpt/foo:geli_keyfile0" geli_gpt/foo_keyfile0_name=3D"/boot/keys/foo.key" So what I did was toss something like this in loader.rc: load_geli -n 0 gpt/foo /boot/keys/foo.key To be completely honest, I find the syntax way more comfortable as well. And it also works quite well. The downside is that since /dev/gpt/foo and /dev/da0 is the exact same = device/partition, GELI will taste both, see the bootflag, and offer to = pass it a phassphrase for both, while I only can (because the keyfile is = only set for one) and want to enable one of them. This means I have to = go through devicecount*password_tries failed attempts at mounting the = devices before actually getting them mounted through the labels. One possible solution to this would be to store a flag in GELIs metadata = about a keyfile being used, and only offer it on boot if the keyfile has = been loaded. I think that would be a bad idea for two reasons: a) This would be similar for passphrase-only devices as well, and b) It would leak the use of a keyfile, which would be bad. Two variants of a solution I'd like though, are: a) Being able to pass an include or exclude list or filter to GELI, = restricting which devices are considered for attachment on boot, b) Being able to pass a flag having GELI only consider = devices/partitions directly or through labels or a) seems like a workable option, while b) would make it impossible to = mix and match, and I suppose it would break some of the modularity of = GEOM that we all like so much I haven't toyed too much with GEOMs internals yet, but if there's a way = for GELI to cleanly check if a direct device has a label attached to it, = then using a global flag to disable boot attach attempts from devices = that also has labels could perhaps be a workable solution, though I = suspect it might be considered a philosophy and bloat issue? Any reason not to allow passing an include or exclude list or filter to = GELI? Just some thoughts, combining GELI and GPT labels carries a lot of = potential for comfortable and adminfriendly encrypted devices, if it = wasn't for this one little thing... (please do point of if I've missed something obvious...) Terje