From owner-freebsd-current@FreeBSD.ORG Mon Jul 13 02:54:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D048D1065672 for ; Mon, 13 Jul 2009 02:54:26 +0000 (UTC) (envelope-from alson+ml@alm.flutnet.org) Received: from tafi.alm.flutnet.org (tafi.dsl.alm.flutnet.org [145.99.245.99]) by mx1.freebsd.org (Postfix) with ESMTP id 3F6C08FC08 for ; Mon, 13 Jul 2009 02:54:26 +0000 (UTC) (envelope-from alson+ml@alm.flutnet.org) Received: from localhost (localhost [127.0.0.1]) by tafi.alm.flutnet.org (Postfix) with ESMTP id 3922078C25 for ; Mon, 13 Jul 2009 04:35:07 +0200 (CEST) X-Virus-Scanned: amavisd-new at alm.flutnet.org Received: from tafi.alm.flutnet.org ([127.0.0.1]) by localhost (tafi.alm.flutnet.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRkycPUEAGvX for ; Mon, 13 Jul 2009 04:34:59 +0200 (CEST) Received: by tafi.alm.flutnet.org (Postfix, from userid 1000) id 697B578C23; Mon, 13 Jul 2009 04:34:59 +0200 (CEST) Date: Mon, 13 Jul 2009 04:34:59 +0200 From: Alson van der Meulen To: freebsd-current@freebsd.org Message-ID: <20090713023459.GA1870@tafi.alm.flutnet.org> Mail-Followup-To: freebsd-current@freebsd.org References: <4A58A056.3020002@haruhiism.net> <200907120824.02622.mel.flynn+fbsd.current@mailing.thruhere.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Disk devices changed after upgrade to current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2009 02:54:27 -0000 * illoai@gmail.com [2009-07-13 03:19]: > 2009/7/12 Mel Flynn : > > I do think this is worth mentioning in UPDATING, perhaps with the advice > > ("strongly recommended") to label partitions before upgrading so that one is > > not depending on device naming conventions in the first place. > > Using the extant ufsid scheme confessedly functionally equivalent > also decrease in anxiety, as fsck clears inodes and I can't tell which > partition, cos /dev/ufsid/beefbeef00f00f looks a lot like anything else > in hexidecimal: like double the symbols of octal. Actually, I recently upgraded from -stable to -current, and the fact that I did use ufsids in -stable caused problems during the upgrade, since they don't appear to work for me in -current: # ls -l /dev/ufsid total 0 crw-r----- 1 root operator 0, 94 Jul 13 04:18 491f4f09c2327891 crw-r----- 1 root operator 0, 90 Jul 13 04:18 494823268ce19306 crw-r----- 1 root operator 0, 92 Jul 13 04:18 49482337897d46de crw-r----- 1 root operator 0, 91 Jul 13 04:18 4948233c348aaa57 crw-r----- 1 root operator 0, 93 Jul 13 04:18 494825678ec6ec4c # /sbin/fsck -p /dev/ufsid/4948233c348aaa57 fsck: cannot open `/dev/ufsid/4948233c348aaa57': Operation not permitted # /sbin/mount /dev/ufsid/4948233c348aaa57 /tmp mount: /dev/ufsid/4948233c348aaa57 : Operation not permitted (/dev/ufsid/4948233c348aaa57 is my /tmp, this was tested in single user mode with only / mounted ro). Fortunately I had the real device names (/dev/mirror/gm0X) still commented out in my fstab, but it definitely didn't make the upgrade any easier. glabels (used for zfs) did continue to work. Alson