From owner-freebsd-geom@FreeBSD.ORG Sun May 31 01:48:01 2009 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 B3C5010656A7 for ; Sun, 31 May 2009 01:48:01 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id 9B48E8FC1D for ; Sun, 31 May 2009 01:48:01 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [172.17.2.19] (jn@stealth.jnielsen.net [74.218.226.254]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id n4V1anYJ020880; Sat, 30 May 2009 21:36:50 -0400 (EDT) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-questions@freebsd.org Date: Sat, 30 May 2009 21:36:49 -0400 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905302136.49369.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-geom@freebsd.org Subject: FreeBSD on USB drive for a MacBook Pro 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: Sun, 31 May 2009 01:48:02 -0000 I'm looking for advice and/or pointers. I have an Intel-based MacBook Pro and I would like to use a USB thumb drive to be able to boot FreeBSD on it. Some questions: 1) Is this even possible? I've read that you _can_ boot Mac OS X from a USB hard drive on a new MacBook but I'm not sure if the same goes for non-Mac OSen or thumb drives. 2) What steps should I take to partition the thing? What boot code should I use and where should it live? I'm planning to do a manual installation in any event. 3) If I manage to get 1 and 2 sorted out, will I be able to boot the same thumb drive on a regular PC? Will any additional steps be necessary? 4) Just to be contrary, I'd also like to use GELI (if possible) for everything but /boot. Does needing an extra /boot partition change anything? I'll be doing some experimenting, but if some things are already known (not) to work I'd like to start with as much info as possible. Thanks, JN From owner-freebsd-geom@FreeBSD.ORG Sun May 31 08:33:07 2009 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 3C9B31065672; Sun, 31 May 2009 08:33:07 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id DDA7D8FC1B; Sun, 31 May 2009 08:33:05 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n4V8WwPt023220; Sun, 31 May 2009 10:32:58 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n4V8WwBv023217; Sun, 31 May 2009 10:32:58 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Sun, 31 May 2009 10:32:58 +0200 (CEST) From: Wojciech Puchar To: John Nielsen In-Reply-To: <200905302136.49369.lists@jnielsen.net> Message-ID: References: <200905302136.49369.lists@jnielsen.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org, freebsd-geom@freebsd.org Subject: Re: FreeBSD on USB drive for a MacBook Pro 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: Sun, 31 May 2009 08:33:07 -0000 > > 4) Just to be contrary, I'd also like to use GELI (if possible) for > everything but /boot. Does needing an extra /boot partition change > anything? Actually you can't create /boot partition, but something else like /b and link /boot to /b/boot bootloader subsystem requires that things are in /boot subdirectory on bootpartition. make /boot partition a, encrypted partition as d and add in loader.conf vfs.root.mountfrom="ufs:da0d.eli" if you do this and not forget to add -b in geli init everything will just work. From owner-freebsd-geom@FreeBSD.ORG Sun May 31 08:34:26 2009 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 6B3C31065678 for ; Sun, 31 May 2009 08:34:26 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id E664F8FC23 for ; Sun, 31 May 2009 08:34:25 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by bwz9 with SMTP id 9so7056649bwz.43 for ; Sun, 31 May 2009 01:34:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=BrpDEj/iMOmni5RdxN5KN7aSshg+SQDpVx16eh2g+TA=; b=QhV1ROvos5PfEe7WAjAMcnSAU47nmQURbqyESdKPfIKh3DGYqEemtJm7nC/RPz+TSc EkO4mqWnVBOlUwYKqodxIwNGFKYo8FJB4wS6ZvQzMCh/huaZRSI5oFEBS9xeZWMGBj96 lkkgL1i6aMA6VMhJMXm6+tlTzejJRMcBQtdiw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; b=hMpnDTHkvnyfrWu5oAUk++71oGDnhe13yCl0RE4udE5+InlPaZA5kGjZUf+srwiVYV WJRmTBqgZLeAVwCuX815XiIP8aw0wVvGbxpRbxpoKjszQPw2EcbizVTdqurtVxpzzM3S N0fErxwok7OfQcpE7avT/Me4/eIDCI6TNNeWk= MIME-Version: 1.0 Received: by 10.204.51.130 with SMTP id d2mr4333501bkg.12.1243757231105; Sun, 31 May 2009 01:07:11 -0700 (PDT) In-Reply-To: <200905302136.49369.lists@jnielsen.net> References: <200905302136.49369.lists@jnielsen.net> From: Chris Rees Date: Sun, 31 May 2009 09:06:51 +0100 Message-ID: To: John Nielsen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org, freebsd-geom@freebsd.org Subject: Re: FreeBSD on USB drive for a MacBook Pro X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2009 08:34:26 -0000 2009/5/31 John Nielsen : > I'm looking for advice and/or pointers. I have an Intel-based MacBook Pro > and I would like to use a USB thumb drive to be able to boot FreeBSD on > it. Some questions: > > 1) Is this even possible? I've read that you _can_ boot Mac OS X from a > USB hard drive on a new MacBook but I'm not sure if the same goes for > non-Mac OSen or thumb drives. Yes. It is possible; as long as you can fit it on. The EFI is quite capable of handling USB sticks. > 2) What steps should I take to partition the thing? What boot code should > I use and where should it live? I'm planning to do a manual installation > in any event. Use Disk Utility, and use GPT layout, as long as you don't care about booting then stick on PCs. > 3) If I manage to get 1 and 2 sorted out, will I be able to boot the same > thumb drive on a regular PC? Will any additional steps be necessary? See above. > 4) Just to be contrary, I'd also like to use GELI (if possible) for > everything but /boot. Does needing an extra /boot partition change > anything? Doubt it, that shouldn't be a problem. See http://www.slax.org/forum.php?action=view&parentID=14468 > I'll be doing some experimenting, but if some things are already known > (not) to work I'd like to start with as much info as possible. > > Thanks, > > JN Good luck. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list? From owner-freebsd-geom@FreeBSD.ORG Mon Jun 1 00:03:33 2009 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 6DD2B106566C for ; Mon, 1 Jun 2009 00:03:33 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from farnsworth.fubar.geek.nz (farnsworth.fubar.geek.nz [69.55.236.47]) by mx1.freebsd.org (Postfix) with ESMTP id 50F718FC19 for ; Mon, 1 Jun 2009 00:03:33 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: by farnsworth.fubar.geek.nz (Postfix, from userid 65534) id 4592833C26; Sun, 31 May 2009 16:45:59 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on farnsworth.fubar.geek.nz X-Spam-Level: * X-Spam-Status: No, score=1.6 required=5.0 tests=AWL,BAYES_00,HELO_LOCALHOST, RCVD_IN_PBL,RDNS_DYNAMIC autolearn=no version=3.2.5 Received: from localhost (125-238-22-134.broadband-telecom.global-gateway.net.nz [125.238.22.134]) by farnsworth.fubar.geek.nz (Postfix) with ESMTP id 4E00633C24 for ; Sun, 31 May 2009 16:45:56 -0700 (PDT) Date: Mon, 1 Jun 2009 11:45:42 +1200 From: Andrew Turner To: freebsd-geom@FreeBSD.org Message-ID: <20090601114542.4cb80938@fubar.geek.nz> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.1; amd64-portbld-freebsd7.1) X-Pirate: Arrrr Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/tST7Qemc8Jc.V/jI_=KC=JS" Cc: Subject: Sending BIO_GETATTR to disks 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, 01 Jun 2009 00:03:33 -0000 --MP_/tST7Qemc8Jc.V/jI_=KC=JS Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline While working on a NAND flash driver I noticed a BIO_GETATTR request will not make it to the disk. It would be useful to support attributes in a NAND layer, eg. to get the size of the OOB region. I've attached a patch to pass the disk driver BIO_GETATTR when the new DISKFLAG_CANGETATTR is set. When DISKFLAG_CANGETATTR is unset it will act the same as currently and deliver ENOIOCTL. Andrew --MP_/tST7Qemc8Jc.V/jI_=KC=JS Content-Type: text/x-patch Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=freebsd-geom_disk.diff Index: geom_disk.c =================================================================== --- geom_disk.c (revision 193190) +++ geom_disk.c (working copy) @@ -306,8 +306,22 @@ break; else if (!strcmp(bp->bio_attribute, "GEOM::kerneldump")) g_disk_kerneldump(bp, dp); - else + else if (!(dp->d_flags & DISKFLAG_CANGETATTR)) error = ENOIOCTL; + else { + bp2 = g_clone_bio(bp); + if (bp2 == NULL) { + g_io_deliver(bp, ENOMEM); + return; + } + bp2->bio_done = g_disk_done; + bp2->bio_disk = dp; + bp2->bio_to = bp->bio_to; + bp2->bio_from = bp->bio_from; + g_disk_lock_giant(dp); + dp->d_strategy(bp2); + g_disk_unlock_giant(dp); + } break; case BIO_FLUSH: g_trace(G_T_TOPOLOGY, "g_disk_flushcache(%s)", Index: geom_disk.h =================================================================== --- geom_disk.h (revision 193190) +++ geom_disk.h (working copy) @@ -90,10 +90,11 @@ void *d_drv1; }; -#define DISKFLAG_NEEDSGIANT 0x1 -#define DISKFLAG_OPEN 0x2 -#define DISKFLAG_CANDELETE 0x4 -#define DISKFLAG_CANFLUSHCACHE 0x8 +#define DISKFLAG_NEEDSGIANT 0x01 +#define DISKFLAG_OPEN 0x02 +#define DISKFLAG_CANDELETE 0x04 +#define DISKFLAG_CANFLUSHCACHE 0x08 +#define DISKFLAG_CANGETATTR 0x10 struct disk *disk_alloc(void); void disk_create(struct disk *disk, int version); --MP_/tST7Qemc8Jc.V/jI_=KC=JS-- From owner-freebsd-geom@FreeBSD.ORG Mon Jun 1 08:38:53 2009 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 77E59106566C; Mon, 1 Jun 2009 08:38:53 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206192061.chello.pl [87.206.192.61]) by mx1.freebsd.org (Postfix) with ESMTP id B247C8FC15; Mon, 1 Jun 2009 08:38:52 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id E5B0245CD8; Mon, 1 Jun 2009 10:06:57 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id AD7CB456AB; Mon, 1 Jun 2009 10:06:43 +0200 (CEST) Date: Mon, 1 Jun 2009 10:06:46 +0200 From: Pawel Jakub Dawidek To: Dmitry Morozovsky Message-ID: <20090601080646.GB1542@garage.freebsd.pl> References: <200905301938.n4UJcpbF017191@svn.freebsd.org> <4A22CFA1.3050408@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZoaI/ZTpAVc4A5k6" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: Doug Barton , freebsd-rc@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: svn commit: r193112 - head/etc/rc.d 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, 01 Jun 2009 08:38:53 -0000 --ZoaI/ZTpAVc4A5k6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 31, 2009 at 11:46:39PM +0400, Dmitry Morozovsky wrote: > On Sun, 31 May 2009, Doug Barton wrote: >=20 > DB> Dmitry Morozovsky wrote: > DB> > Doug, > DB> >=20 > DB> > On Sat, 30 May 2009, Doug Barton wrote: > DB> >=20 > DB> > DB> Author: dougb > DB> > DB> Date: Sat May 30 19:38:51 2009 > DB> > DB> New Revision: 193112 > DB> > DB> URL: http://svn.freebsd.org/changeset/base/193112 > DB> > DB>=20 > DB> > DB> Log: > DB> > DB> As previously advertised, remove this script prior to the 8.0= branch. > DB> >=20 > DB> > Was there an agreement what should one do with dumping to gmirror (= see=20 > DB> > sbin/geom/class/mirror/gmirror.8) ? > DB>=20 > DB> I'm not familiar with that issue, but it sounds like something that > DB> needs its own rc.d script. If someone who knows what is supposed to > DB> happen wants to write something up and send it to the freebsd-rc@ list > DB> I'll be glad to help review it. >=20 > Something like (checks should be added, yeah) >=20 > #!/bin/sh > # > # $FreeBSD$ > # >=20 > # BEFORE: savecore > # PROVIDE: gmirror-savecore > # KEYWORD: nojail >=20 > . /etc/rc.subr >=20 > name=3D"gmirror_savecore" > start_cmd=3D"gmsavecore_start" > stop_cmd=3D":" >=20 > gmsavecore_start() > { > gmirror configure -b prefer /dev/dumpdev > } >=20 > load_rc_config $name > run_rc_command "$1" >=20 > possibly? It's not that simple... First you have to remember previous balance algorithm and recover it once dumping crash dump is done. You also have to check if dumpdev is placed somewhere on a gmirror provider, which is not that simple, unfortunately. Imagine your dump partition is called /dev/label/dump and there is a long way to gmirror provider: label/dump -> mirror/root0s1b -> mirror/root0s1 -> mirror/root0 You can't just call 'gmirror configure -b prefer /dev/label/dump'. I'm happy to review another patch, but I don't really have any bright idea of how this should be implemented:) --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ZoaI/ZTpAVc4A5k6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKI4wWForvXbEpPzQRAtlnAJ953a3o8UZrK57x5eJqHoKHOdHxbQCg8ICM ZjIYwj9rl6E2vKu5DmyGnTw= =YC9W -----END PGP SIGNATURE----- --ZoaI/ZTpAVc4A5k6-- From owner-freebsd-geom@FreeBSD.ORG Mon Jun 1 11:06:51 2009 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 C692010656C6 for ; Mon, 1 Jun 2009 11:06:51 +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 ACA1B8FC1C for ; Mon, 1 Jun 2009 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n51B6pjf021075 for ; Mon, 1 Jun 2009 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n51B6pxt021071 for freebsd-geom@FreeBSD.org; Mon, 1 Jun 2009 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 1 Jun 2009 11:06:51 GMT Message-Id: <200906011106.n51B6pxt021071@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, 01 Jun 2009 11:06:57 -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/134922 geom kernel panic when use fdisk on disk who been removed f o kern/134113 geom [geli] Problem setting secondary GELI key o kern/134044 geom [geom] gmirror(8) overwrites fs with stale data from r 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/132242 geom [gmirror] gmirror.ko fails to fully initialize o kern/131353 geom [geom] gjournal(8) kernel lock o kern/131037 geom [geli] Unable to create disklabel on .eli-Device p docs/130548 geom [patch] gjournal(8) man page is missing sysctls o kern/130528 geom gjournal fsck during boot 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 o bin/128398 geom [patch] glabel(8): teach geom_label to recognise gpt l f kern/128276 geom [gmirror] machine lock up when gmirror module is used o kern/126902 geom [geom] geom_label: kernel panic during install boot 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/124294 geom [geom] gmirror(8) have inappropriate logic when workin o kern/124130 geom [gmirror] [usb] gmirror fails to start usb devices tha o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123630 geom [patch] [gmirror] gmirror doesnt allow the original dr o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/122738 geom [geom] gmirror list "losts consumers" after gmirror de f kern/122415 geom [geom] UFS labels are being constantly created and rem o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121559 geom [patch] [geom] geom label class allows to create inacc o kern/121481 geom [gmirror] data rot on disk with gmirror o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120231 geom [geom] GEOM_CONCAT error adding second drive o kern/120091 geom [geom] [geli] [gjournal] geli does not prompt for pass o kern/120044 geom [msdosfs] [geom] incorrect MSDOSFS label fries adminis o kern/120021 geom [geom] [panic] net-p2p/qbittorrent crashes system when o kern/119743 geom [geom] geom label for cds is keeped after dismount and p kern/116896 geom [geom] [patch] Typo in a kassert in GEOM 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 o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad o kern/113885 geom [gmirror] [patch] improved gmirror balance algorithm o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back p bin/110705 geom gmirror(8) control utility does not exit with correct o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach 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 a kern/89660 geom [vinum] [patch] [panic] due to g_malloc returning null o kern/89546 geom [geom] GEOM error s kern/89102 geom [geom] [panic] panic when forced unmount FS from unplu 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 kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o bin/81779 geom misleading error messages in geom(8) utilities. 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. s kern/73177 geom kldload geom_* causes panic due to memory exhaustion 61 problems total. From owner-freebsd-geom@FreeBSD.ORG Mon Jun 1 19:23:34 2009 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 50F371065754 for ; Mon, 1 Jun 2009 19:23:34 +0000 (UTC) (envelope-from don_read@att.net) Received: from smtp109.sbc.mail.mud.yahoo.com (smtp109.sbc.mail.mud.yahoo.com [68.142.198.208]) by mx1.freebsd.org (Postfix) with SMTP id F08498FC0C for ; Mon, 1 Jun 2009 19:23:33 +0000 (UTC) (envelope-from don_read@att.net) Received: (qmail 20190 invoked from network); 1 Jun 2009 18:56:53 -0000 Received: from unknown (HELO localhost) (don_read@74.235.245.154 with login) by smtp109.sbc.mail.mud.yahoo.com with SMTP; 1 Jun 2009 18:56:52 -0000 X-Yahoo-Newman-Property: ymail-3 Date: Mon, 1 Jun 2009 14:56:50 -0400 From: Don Read To: John Nielsen Message-ID: <20090601145650.5cef1601@att.net> In-Reply-To: <200905302136.49369.lists@jnielsen.net> References: <200905302136.49369.lists@jnielsen.net> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.1; i386-portbld-freebsd6.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org, freebsd-geom@freebsd.org Subject: Re: FreeBSD on USB drive for a MacBook Pro 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, 01 Jun 2009 19:23:34 -0000 On Sat, 30 May 2009 21:36:49 -0400 John Nielsen said: > I'm looking for advice and/or pointers. I have an Intel-based MacBook Pro > and I would like to use a USB thumb drive to be able to boot FreeBSD on > it. This should get you started: http://groups.google.com/group/lucky.freebsd.questions/msg/5c759b1c87376b22?pli=1 Regards, -- Don Read don_read@att.net It's always darkest before the dawn. So if you are going to steal the neighbor's newspaper, that's the time to do it. From owner-freebsd-geom@FreeBSD.ORG Tue Jun 2 11:27:53 2009 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 034411065672 for ; Tue, 2 Jun 2009 11:27:53 +0000 (UTC) (envelope-from stadtkind2@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 4D7258FC19 for ; Tue, 2 Jun 2009 11:27:52 +0000 (UTC) (envelope-from stadtkind2@gmx.de) Received: (qmail invoked by alias); 02 Jun 2009 11:01:11 -0000 Received: from h1365724.stratoserver.net (EHLO apfel.example.net) [85.214.116.165] by mail.gmx.net (mp007) with SMTP; 02 Jun 2009 13:01:11 +0200 X-Authenticated: #42330871 X-Provags-ID: V01U2FsdGVkX18M9GAMAh4M7LN8p/7kV6t9n1lgQuXxcpq4lAqajb qcIruxsdc6TbTb Message-ID: <4A250674.7080706@gmx.de> Date: Tue, 02 Jun 2009 13:01:08 +0200 From: =?ISO-8859-1?Q?Stefan_Kr=FCger?= User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.57 Subject: problems using geli on top of gmirror 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: Tue, 02 Jun 2009 11:27:53 -0000 hello list, I have some problems using geli and gmirror (gm0 consists of ad0 and ad2) together, here's my test-setup: $ uname -sr FreeBSD 7.2-RELEASE $ ls -hl /dev/mirror/gm0s1* crw-r----- 1 root operator 0, 76 Jun 2 12:17 /dev/mirror/gm0s1 crw-r----- 1 root operator 0, 77 Jun 2 12:17 /dev/mirror/gm0s1a crw-r----- 1 root operator 0, 78 Jun 2 12:17 /dev/mirror/gm0s1b crw-r----- 1 root operator 0, 91 Jun 2 12:17 /dev/mirror/gm0s1b.eli crw-r----- 1 root operator 0, 79 Jun 2 12:17 /dev/mirror/gm0s1c crw-r----- 1 root operator 0, 80 Jun 2 12:21 /dev/mirror/gm0s1d # bsdlabel /dev/mirror/gm0s1 # /dev/mirror/gm0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 8388608 0 4.2BSD 2048 16384 28552 b: 2097152 8388608 swap c: 12583809 0 unused 0 0 # "raw" part, don't edit d: 2098049 10485760 4.2BSD 2048 16384 28552 As you can see, encrypting the swap partition with # geli onetime -s 4096 -d /dev/mirror/gm0s1b already worked fine, but trying to do # geli init -s 4096 -K /boot/keys/gm0s1d.key /dev/mirror/gm0s1d returns geli: Cannot store metadata on /dev/mirror/gm0s1d: No such file or directory so my question is, is that even possible? and if yes, what wrong with my setup? From owner-freebsd-geom@FreeBSD.ORG Wed Jun 3 22:11:53 2009 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 7CC4D1065675 for ; Wed, 3 Jun 2009 22:11:53 +0000 (UTC) (envelope-from dan.naumov@gmail.com) Received: from mail-gx0-f210.google.com (mail-gx0-f210.google.com [209.85.217.210]) by mx1.freebsd.org (Postfix) with ESMTP id 38F408FC15 for ; Wed, 3 Jun 2009 22:11:53 +0000 (UTC) (envelope-from dan.naumov@gmail.com) Received: by gxk6 with SMTP id 6so186887gxk.19 for ; Wed, 03 Jun 2009 15:11:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=YkprYYXmZQuPgCklvBhobeDK162Bn1YmPa4w/iSnrNA=; b=sFCKNfM7E4+PpZ9xi640V7sMOD+zdmQaq5eOsjC8SSbDo5zminBpNFpVupgpRBZfAD IaVCOTC0GC/LSxa4v6o1RrmzFE1Iump/wus+0+dXoFfYhIgWNv3JA3ovo3j+1AYiyMQB F7H8fgmOQtPKg68C3MAbsmuVqJKDXO5R70NFI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=Tr24QT2A10anF1FgtuxaG09gHfjoNatBh3ZQ+fSz7Xx3sjFf7VL30y6/wy7pYdS6aJ n8m2dhy1s0HTaxnRAkrvJxsQUfsBogGM+fTZ4xwOSu1H3W4DhNZWKmu2an/dAx2e7mUl HDmctAvIrx1rL4vIE5Kx2bT6ggQTPBG0BmHPU= MIME-Version: 1.0 Received: by 10.100.10.15 with SMTP id 15mr1886777anj.8.1244067112567; Wed, 03 Jun 2009 15:11:52 -0700 (PDT) Date: Thu, 4 Jun 2009 01:11:52 +0300 Message-ID: From: Dan Naumov To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: GELI and dynamically sized file providers? 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, 03 Jun 2009 22:11:53 -0000 Hello list. As far as I know, this feature hasn't been implemented (if it is, by all means please educate me on this) and I think it would make a really good addition to the current options of using GELI encryption on FreeBSD. What I want is to have data encrypted with GELI and kept inside an encrypted file that is held on a regular ZFS or UFS2 partition. Now I know it is possible to just dd an arbitrarily sized block of data as a file onto the partition and use it as a provider for GELI, but this has a very serious limitation: you cannot resize this file without essentially have to move all your data out, delete the provider, create a new smaller/bigger file, use it as a new provider for GELI and then move the data back inside it. This is really really cumbersome. What would be really nice is to have this block of data used as a provider to dynamically grow or shrink as more or less is needed to store the encrypted files. This would open up a lot of options for the user: 1) You would be able to start small and then grow your amount of encrypted data for as long as you have free space on the ZFS / UFS2 partition holding the dynamic file provider. 2) If you end up overestimating your need for the amount of data you want to be encrypted, the provider shrinks accordingly, leaving more space free on the ZFS / UFS2 partition for use for unencrypted data without any speed penalties that come with using encryption. 3) This makes combining data redundancy and encryption a LOT easier: for example you can have a 4 disk ZFS raidz of 2tb disks (resulting in 6tb of space usable) and a dynamic file provider kept on this raidz than grows or shrinks according to space requirements of the encrypted files AND your data integrity and redundancy is on the shoulders of ZFS instead of having the user ponder the most non-insane way of doing things and avoiding things like having to keep separate partitions used as providers for 4 different GELI devices that each have to be "opened" with a passkey before the ZFS pool can be brought online or having to keep one ENORMOUS file container inside the ZFS pool taking up a lot of space without you ever knowing if you are going to ever use it all. - Dan Naumov From owner-freebsd-geom@FreeBSD.ORG Thu Jun 4 09:00:30 2009 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 98AD4106564A for ; Thu, 4 Jun 2009 09:00:30 +0000 (UTC) (envelope-from bo.coopci@i-waihui.com) Received: from mail-px0-f199.google.com (mail-px0-f199.google.com [209.85.216.199]) by mx1.freebsd.org (Postfix) with ESMTP id 7A8B18FC08 for ; Thu, 4 Jun 2009 09:00:30 +0000 (UTC) (envelope-from bo.coopci@i-waihui.com) Received: by pxi37 with SMTP id 37so624871pxi.3 for ; Thu, 04 Jun 2009 02:00:30 -0700 (PDT) Received: by 10.114.15.9 with SMTP id 9mr2089464wao.82.1244104306878; Thu, 04 Jun 2009 01:31:46 -0700 (PDT) Received: from ?10.217.15.144? ([61.135.152.194]) by mx.google.com with ESMTPS id n6sm3245207wag.4.2009.06.04.01.31.43 (version=SSLv3 cipher=RC4-MD5); Thu, 04 Jun 2009 01:31:45 -0700 (PDT) Message-ID: <4A27866D.6010103@gmail.com> Date: Thu, 04 Jun 2009 16:31:41 +0800 From: cooper User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit Subject: Questions about g_mbr and g_bsd 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, 04 Jun 2009 09:00:30 -0000 g_mbr_start and g_bsd_start care only if (bp->bio_cmd == BIO_GETATTR). Does anyone know why they neither do somthing similar to g_disk_start nor invoke the underlying g_disk? Thanks From owner-freebsd-geom@FreeBSD.ORG Thu Jun 4 09:26:23 2009 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 715AF106566C for ; Thu, 4 Jun 2009 09:26:23 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 377F88FC15 for ; Thu, 4 Jun 2009 09:26:23 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id EEBC269959; Thu, 4 Jun 2009 09:10:21 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id n549AXil010766; Thu, 4 Jun 2009 09:10:33 GMT (envelope-from phk@critter.freebsd.dk) To: cooper From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 04 Jun 2009 16:31:41 +0800." <4A27866D.6010103@gmail.com> Date: Thu, 04 Jun 2009 09:10:33 +0000 Message-ID: <10765.1244106633@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: freebsd-geom@freebsd.org Subject: Re: Questions about g_mbr and g_bsd 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, 04 Jun 2009 09:26:23 -0000 In message <4A27866D.6010103@gmail.com>, cooper writes: >g_mbr_start and g_bsd_start care only if (bp->bio_cmd == BIO_GETATTR). >Does anyone know why they neither do somthing similar to g_disk_start >nor invoke the underlying g_disk? No they dont, all other request types are handled by the "slicer" code which they control with data structures describing the layout. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-geom@FreeBSD.ORG Thu Jun 4 23:49:06 2009 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 2705A1065670 for ; Thu, 4 Jun 2009 23:49:06 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: from mail-gx0-f207.google.com (mail-gx0-f207.google.com [209.85.217.207]) by mx1.freebsd.org (Postfix) with ESMTP id E39BB8FC18 for ; Thu, 4 Jun 2009 23:49:05 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: by gxk3 with SMTP id 3so651518gxk.19 for ; Thu, 04 Jun 2009 16:49:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.90.106.3 with SMTP id e3mr2312202agc.54.1244157509996; Thu, 04 Jun 2009 16:18:29 -0700 (PDT) From: Juli Mallett Date: Thu, 4 Jun 2009 16:18:09 -0700 Message-ID: To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Is anything being done to un-break partition names? 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, 04 Jun 2009 23:49:06 -0000 Hey folks, If I install 7.2 (or old 8-CURRENT) and partition a drive "dangerously dedicated" and answer No when asked if I want to create a true partition entry, and then install as normal, my system is set up with partitions named like da0s1a. Newer 8-CURRENT instead names the devices da0a, which means root mount fails, etc., until one updates /etc/fstab. This also seems to confuse sysinstall, which appears to expect labeling da0s1 to work even if you're in dangerously-dedicated mode =97 though I might be misunderstanding the interactions there; randi@ suggests it's just a problem with sanitizing disk names in libdisk, although when I built sysinstall with a patched libdisk and tried to use it when booting from an 8-CURRENT (snapshot as of a few weeks back) livefs disk, it seemed to have other problems with the device names. This seems like a huge POLA violation and has eaten several hours of my life in terms of fixing servers that were tracking 8-CURRENT and failed to boot up because of the need to change /etc/fstab that wasn't documented in UPDATING. Is anything being done to add compatibility slice names, or to teach mergemaster about the change? I don't know enough about what all is going on on disk to know whether this is something that just affects dangerously-dedicated disks, but it seems to be consistently biting me, and I can only imagine how much trouble it's going to cause others. Was this change even intentional? Juli. From owner-freebsd-geom@FreeBSD.ORG Fri Jun 5 05:12:09 2009 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 7F467106564A for ; Fri, 5 Jun 2009 05:12:09 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206192061.chello.pl [87.206.192.61]) by mx1.freebsd.org (Postfix) with ESMTP id C7F938FC19 for ; Fri, 5 Jun 2009 05:12:07 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 0AA2D456AB; Fri, 5 Jun 2009 07:12:06 +0200 (CEST) Received: from localhost (chello087206192061.chello.pl [87.206.192.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id A002145685; Fri, 5 Jun 2009 07:12:00 +0200 (CEST) Date: Fri, 5 Jun 2009 07:12:04 +0200 From: Pawel Jakub Dawidek To: Juli Mallett Message-ID: <20090605051203.GD1705@garage.freebsd.pl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7CZp05NP8/gJM8Cl" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: marcel@FreeBSD.org, freebsd-geom@freebsd.org Subject: Re: Is anything being done to un-break partition names? 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, 05 Jun 2009 05:12:09 -0000 --7CZp05NP8/gJM8Cl Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 04, 2009 at 04:18:09PM -0700, Juli Mallett wrote: > Hey folks, >=20 > If I install 7.2 (or old 8-CURRENT) and partition a drive "dangerously > dedicated" and answer No when asked if I want to create a true > partition entry, and then install as normal, my system is set up with > partitions named like da0s1a. Newer 8-CURRENT instead names the > devices da0a, which means root mount fails, etc., until one updates > /etc/fstab. This also seems to confuse sysinstall, which appears to > expect labeling da0s1 to work even if you're in dangerously-dedicated > mode =E2=80=94 though I might be misunderstanding the interactions there; > randi@ suggests it's just a problem with sanitizing disk names in > libdisk, although when I built sysinstall with a patched libdisk and > tried to use it when booting from an 8-CURRENT (snapshot as of a few > weeks back) livefs disk, it seemed to have other problems with the > device names. >=20 > This seems like a huge POLA violation and has eaten several hours of > my life in terms of fixing servers that were tracking 8-CURRENT and > failed to boot up because of the need to change /etc/fstab that wasn't > documented in UPDATING. I was bitten by the exactly the same thing. Unfortunately in my case I was upgrading from 7.0 or something and kernel.old didn't work for me with new userland. So I had to compile GEOM_PART_MBR out and compiled GEOM_MBR in, everything on another machine and then transfer new kernel using nc(1) and tar(1), because sshd(8) didn't work properly. And I was in a hury. All in all, a huge disappointment. BTW. I wasn't able to boot my system using ufs:/dev/ad0a on mountroot prompt. > Is anything being done to add compatibility slice names, or to teach > mergemaster about the change? I don't know enough about what all is > going on on disk to know whether this is something that just affects > dangerously-dedicated disks, but it seems to be consistently biting > me, and I can only imagine how much trouble it's going to cause > others. Was this change even intentional? I don't think it was. For me it's a bug in GEOM_PART_MBR, which has problems detecting MBRs properly. Shame on you, Marcel!:) --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --7CZp05NP8/gJM8Cl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKKKkjForvXbEpPzQRAnn3AKDAMZ9QP7HZ8hq0Ei11FDwpaWqxHQCbB4td O3mUBeDwMocGz0N1GV/5XhU= =gmuT -----END PGP SIGNATURE----- --7CZp05NP8/gJM8Cl-- From owner-freebsd-geom@FreeBSD.ORG Fri Jun 5 20:05:18 2009 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 AA878106564A; Fri, 5 Jun 2009 20:05:18 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206192061.chello.pl [87.206.192.61]) by mx1.freebsd.org (Postfix) with ESMTP id 0B6748FC15; Fri, 5 Jun 2009 20:05:17 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id C84C0456AB; Fri, 5 Jun 2009 22:05:15 +0200 (CEST) Received: from localhost (chello087206192061.chello.pl [87.206.192.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id D3C4B45685; Fri, 5 Jun 2009 22:05:09 +0200 (CEST) Date: Fri, 5 Jun 2009 22:05:13 +0200 From: Pawel Jakub Dawidek To: Marcel Moolenaar Message-ID: <20090605200512.GA2313@garage.freebsd.pl> References: <20090605051203.GD1705@garage.freebsd.pl> <46FB00ED-62DC-4924-A84A-8C34B26DA22E@mac.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <46FB00ED-62DC-4924-A84A-8C34B26DA22E@mac.com> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: marcel@FreeBSD.org, Juli Mallett , freebsd-geom@freebsd.org Subject: Re: Is anything being done to un-break partition names? 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, 05 Jun 2009 20:05:19 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 05, 2009 at 12:26:04PM -0700, Marcel Moolenaar wrote: >=20 > On Jun 4, 2009, at 10:12 PM, Pawel Jakub Dawidek wrote: >=20 > >On Thu, Jun 04, 2009 at 04:18:09PM -0700, Juli Mallett wrote: > >>Hey folks, > >> > >>If I install 7.2 (or old 8-CURRENT) and partition a drive =20 > >>"dangerously > >>dedicated" and answer No when asked if I want to create a true > >>partition entry, and then install as normal, my system is set up with > >>partitions named like da0s1a. >=20 > That's your problem. In a DD setup, you don't have slices. >=20 > >> Newer 8-CURRENT instead names the > >>devices da0a, >=20 > This is correct. >=20 > > > >I don't think it was. For me it's a bug in GEOM_PART_MBR, which has > >problems detecting MBRs properly. > > > >Shame on you, Marcel!:) >=20 > The bug is on your disk and as such in sysinstall. GEOM_PART_MBR > detects the MBR just fine. If you don't have GEOM_PART_BSD in > your kernel your will in fact get the MBR slices. The problem > for you is in the fact that you have a BSD disklabel in sector > 2, which takes precedence. A disk partitioned as a BSD disklabel > nested in an MBR slice can *NEVER* have a BSD disklabel in the > 2nd sector on the disk. The fact that there is a BSD disklabel > in sector 2 means that the disk is DD and that is what you get > for gpart. This is interesting: bridge:root:~# bsdlabel /dev/ad0 # /dev/ad0: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 10497792 16 unused 0 0 =20 b: 2097152 10497808 swap =20 c: 12594960 0 unused 0 0 # "raw" part, don't= edit bridge:root:~# bsdlabel /dev/ad0s1 # /dev/ad0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 12070609 524288 4.2BSD 2048 16384 28552=20 b: 524288 0 swap =20 c: 12594897 0 unused 0 0 # "raw" part, don't= edit Anyway, why BSD disklabel takes precedence over MBR for gpart? Are you happy with users upgrading their system and finding it no longer boots? I think that even a note in UPDATING is not enough, we should really make it to just work after the upgrade. Why not to change priorities and accept MBR first? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKKXp4ForvXbEpPzQRAhTMAKCFXlakn3hSs2EQmmKdY8bIDFY0QACgmbcb UtaV7UDeX8TyYWVB6GBUrAI= =U87Y -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- From owner-freebsd-geom@FreeBSD.ORG Fri Jun 5 20:14:54 2009 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 738B010656A9; Fri, 5 Jun 2009 20:14:54 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: from mail-gx0-f206.google.com (mail-gx0-f206.google.com [209.85.217.206]) by mx1.freebsd.org (Postfix) with ESMTP id CA25A8FC1F; Fri, 5 Jun 2009 20:14:53 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: by gxk2 with SMTP id 2so20158gxk.12 for ; Fri, 05 Jun 2009 13:14:53 -0700 (PDT) MIME-Version: 1.0 Sender: juli@clockworksquid.com Received: by 10.90.96.1 with SMTP id t1mr2667438agb.43.1244232893194; Fri, 05 Jun 2009 13:14:53 -0700 (PDT) In-Reply-To: <46FB00ED-62DC-4924-A84A-8C34B26DA22E@mac.com> References: <20090605051203.GD1705@garage.freebsd.pl> <46FB00ED-62DC-4924-A84A-8C34B26DA22E@mac.com> From: Juli Mallett Date: Fri, 5 Jun 2009 13:14:33 -0700 X-Google-Sender-Auth: 4b49b52c460cf63c Message-ID: To: Marcel Moolenaar Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: Pawel Jakub Dawidek , freebsd-geom@freebsd.org Subject: Re: Is anything being done to un-break partition names? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jmallett@freebsd.org List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2009 20:14:55 -0000 On Fri, Jun 5, 2009 at 12:26 PM, Marcel Moolenaar wrote: > On Jun 4, 2009, at 10:12 PM, Pawel Jakub Dawidek wrote: >> On Thu, Jun 04, 2009 at 04:18:09PM -0700, Juli Mallett wrote: >>> >>> Hey folks, >>> >>> If I install 7.2 (or old 8-CURRENT) and partition a drive "dangerously >>> dedicated" and answer No when asked if I want to create a true >>> partition entry, and then install as normal, my system is set up with >>> partitions named like da0s1a. > > That's your problem. In a DD setup, you don't have slices. I'm not arguing about whether the names are technically correct =97 I'm concerned about POLA violations and the undocumented breakage of legitimately-installed systems. Could you please at least document this in UPDATING? It's a pretty major change and I wouldn't be so cavalier as to dismiss it as the problem of the users in question. DD configurations have worked historically and have been upgradable. I presume that the owner of libdisk/sysinstall will fix sysinstall's expectations of DD disks or remove support for them (and remove support for upgrading them or installing to disks which have already been partitioned and labeled which are DD.) Juli. From owner-freebsd-geom@FreeBSD.ORG Fri Jun 5 20:26:04 2009 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 E1A8B106566B; Fri, 5 Jun 2009 20:26:04 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id A57EE8FC17; Fri, 5 Jun 2009 20:26:04 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.64.3]) by phk.freebsd.dk (Postfix) with ESMTP id 511EF69959; Fri, 5 Jun 2009 20:26:03 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id n55KQFoq007194; Fri, 5 Jun 2009 20:26:15 GMT (envelope-from phk@critter.freebsd.dk) To: jmallett@freebsd.org From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 05 Jun 2009 13:14:33 MST." Date: Fri, 05 Jun 2009 20:26:15 +0000 Message-ID: <7193.1244233575@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Marcel Moolenaar , Pawel Jakub Dawidek , freebsd-geom@freebsd.org Subject: Re: Is anything being done to un-break partition names? 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, 05 Jun 2009 20:26:05 -0000 In message , Juli Mallett writes: >> That's your problem. In a DD setup, you don't have slices. > >I'm not arguing about whether the names are technically correct =97 I'm >concerned about POLA violations and the undocumented breakage of >legitimately-installed systems. DD has not been "legitimate" since 4.x releases. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-geom@FreeBSD.ORG Fri Jun 5 20:26:15 2009 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 4B726106564A for ; Fri, 5 Jun 2009 20:26:15 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout017.mac.com (asmtpout017.mac.com [17.148.16.92]) by mx1.freebsd.org (Postfix) with ESMTP id 367EF8FC0A for ; Fri, 5 Jun 2009 20:26:13 +0000 (UTC) (envelope-from xcllnt@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [172.24.105.139] (natint3.juniper.net [66.129.224.36]) by asmtp017.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KKS005OS5ZG0Y60@asmtp017.mac.com>; Fri, 05 Jun 2009 12:26:05 -0700 (PDT) Message-id: <46FB00ED-62DC-4924-A84A-8C34B26DA22E@mac.com> From: Marcel Moolenaar To: Pawel Jakub Dawidek In-reply-to: <20090605051203.GD1705@garage.freebsd.pl> Date: Fri, 05 Jun 2009 12:26:04 -0700 References: <20090605051203.GD1705@garage.freebsd.pl> X-Mailer: Apple Mail (2.935.3) Cc: marcel@FreeBSD.org, Juli Mallett , freebsd-geom@freebsd.org Subject: Re: Is anything being done to un-break partition names? 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, 05 Jun 2009 20:26:15 -0000 On Jun 4, 2009, at 10:12 PM, Pawel Jakub Dawidek wrote: > On Thu, Jun 04, 2009 at 04:18:09PM -0700, Juli Mallett wrote: >> Hey folks, >> >> If I install 7.2 (or old 8-CURRENT) and partition a drive >> "dangerously >> dedicated" and answer No when asked if I want to create a true >> partition entry, and then install as normal, my system is set up with >> partitions named like da0s1a. That's your problem. In a DD setup, you don't have slices. >> Newer 8-CURRENT instead names the >> devices da0a, This is correct. > > I don't think it was. For me it's a bug in GEOM_PART_MBR, which has > problems detecting MBRs properly. > > Shame on you, Marcel!:) The bug is on your disk and as such in sysinstall. GEOM_PART_MBR detects the MBR just fine. If you don't have GEOM_PART_BSD in your kernel your will in fact get the MBR slices. The problem for you is in the fact that you have a BSD disklabel in sector 2, which takes precedence. A disk partitioned as a BSD disklabel nested in an MBR slice can *NEVER* have a BSD disklabel in the 2nd sector on the disk. The fact that there is a BSD disklabel in sector 2 means that the disk is DD and that is what you get for gpart. FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-geom@FreeBSD.ORG Fri Jun 5 20:38:34 2009 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 D641B106564A; Fri, 5 Jun 2009 20:38:34 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout015.mac.com (asmtpout015.mac.com [17.148.16.90]) by mx1.freebsd.org (Postfix) with ESMTP id BEB868FC0C; Fri, 5 Jun 2009 20:38:34 +0000 (UTC) (envelope-from xcllnt@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [172.24.105.139] (natint3.juniper.net [66.129.224.36]) by asmtp015.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KKS00BOH9C9CN00@asmtp015.mac.com>; Fri, 05 Jun 2009 13:38:34 -0700 (PDT) Message-id: <5BE6CEC9-8F49-473B-A3E4-2702680A8836@mac.com> From: Marcel Moolenaar To: Pawel Jakub Dawidek In-reply-to: <20090605200512.GA2313@garage.freebsd.pl> Date: Fri, 05 Jun 2009 13:38:33 -0700 References: <20090605051203.GD1705@garage.freebsd.pl> <46FB00ED-62DC-4924-A84A-8C34B26DA22E@mac.com> <20090605200512.GA2313@garage.freebsd.pl> X-Mailer: Apple Mail (2.935.3) Cc: marcel@FreeBSD.org, Juli Mallett , freebsd-geom@freebsd.org Subject: Re: Is anything being done to un-break partition names? 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, 05 Jun 2009 20:38:35 -0000 On Jun 5, 2009, at 1:05 PM, Pawel Jakub Dawidek wrote: > On Fri, Jun 05, 2009 at 12:26:04PM -0700, Marcel Moolenaar wrote: >> >> On Jun 4, 2009, at 10:12 PM, Pawel Jakub Dawidek wrote: >> >>> On Thu, Jun 04, 2009 at 04:18:09PM -0700, Juli Mallett wrote: >>>> Hey folks, >>>> >>>> If I install 7.2 (or old 8-CURRENT) and partition a drive >>>> "dangerously >>>> dedicated" and answer No when asked if I want to create a true >>>> partition entry, and then install as normal, my system is set up >>>> with >>>> partitions named like da0s1a. >> >> That's your problem. In a DD setup, you don't have slices. >> >>>> Newer 8-CURRENT instead names the >>>> devices da0a, >> >> This is correct. >> >>> >>> I don't think it was. For me it's a bug in GEOM_PART_MBR, which has >>> problems detecting MBRs properly. >>> >>> Shame on you, Marcel!:) >> >> The bug is on your disk and as such in sysinstall. GEOM_PART_MBR >> detects the MBR just fine. If you don't have GEOM_PART_BSD in >> your kernel your will in fact get the MBR slices. The problem >> for you is in the fact that you have a BSD disklabel in sector >> 2, which takes precedence. A disk partitioned as a BSD disklabel >> nested in an MBR slice can *NEVER* have a BSD disklabel in the >> 2nd sector on the disk. The fact that there is a BSD disklabel >> in sector 2 means that the disk is DD and that is what you get >> for gpart. > > This is interesting: > > bridge:root:~# bsdlabel /dev/ad0 > # /dev/ad0: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 10497792 16 unused 0 0 > b: 2097152 10497808 swap > c: 12594960 0 unused 0 0 # "raw" part, > don't edit > bridge:root:~# bsdlabel /dev/ad0s1 > # /dev/ad0s1: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 12070609 524288 4.2BSD 2048 16384 28552 > b: 524288 0 swap > c: 12594897 0 unused 0 0 # "raw" part, > don't edit > > Anyway, why BSD disklabel takes precedence over MBR for gpart? The BSD disklabel has an MBR immediately preceding it. While the MBR by definition has no valid partition information, there are 2 reasons not to take this too seriously during the taste: 1. By design GPT can only have a PMBR, but this has not been enforced in practice. As such, the existence of valid MBR slices is not a reason to ignore the GPT. The BSD disklabel follows this principle by virtue of having a MBR compliant boot record immediately ahead of it, like GPT. 2. False negatives cannot not be eliminated when ignoring the BSD disklabel when the MBR has slices. It's better to bank on the fact that there cannot be a BSD disklabel immediately following the MBR when that disklabel is actually nested and inside a MBR slice. Thus the existence of the BSD disklabel in sector 2 is enough proof that the MBR is part of the BSD disklabel and not on its own. Just like with GPT. > Are you happy with users upgrading their system and finding it no > longer > boots? I'm not happy about it, but I haven't found an acceptable solution until this discussion (but see below). > I think that even a note in UPDATING is not enough, we should really > make it to just work after the upgrade. Why not to change priorities > and > accept MBR first? That introduces significant breakages in normal setups. The priority should not be changed. It's resulting in the right behaviour and any exceptions to that (i.e. we need the wrong behaviour) should be coded explicitly. The closest we can get is by having the BSD disklabel code check if there are valid MBR partitions defined and if yes, back-off. This covers exactly the problem case and doesn't introduce false negatives in other scenarios. But: we should fix sysinstall as well. Either we should finally rip out DD or we should have it create proper DD images... -- Marcel Moolenaar xcllnt@mac.com