From owner-freebsd-current@FreeBSD.ORG Mon Jul 13 06:59:39 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 64BCB106566C for ; Mon, 13 Jul 2009 06:59:39 +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 1A69C8FC1B for ; Mon, 13 Jul 2009 06:59:39 +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 6106D78C25 for ; Mon, 13 Jul 2009 08:59:38 +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 ch6gjxvYKEeC for ; Mon, 13 Jul 2009 08:59:28 +0200 (CEST) Received: by tafi.alm.flutnet.org (Postfix, from userid 1000) id 8239D78C23; Mon, 13 Jul 2009 08:59:28 +0200 (CEST) Date: Mon, 13 Jul 2009 08:59:28 +0200 From: Alson van der Meulen To: freebsd-current@freebsd.org Message-ID: <20090713065928.GB3645@tafi.alm.flutnet.org> Mail-Followup-To: freebsd-current@freebsd.org References: <200907122143.26830.mel.flynn+fbsd.current@mailing.thruhere.net> <20090713060456.GA2565@tafi.alm.flutnet.org> <200907122231.44564.mel.flynn+fbsd.current@mailing.thruhere.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200907122231.44564.mel.flynn+fbsd.current@mailing.thruhere.net> 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 06:59:39 -0000 * Mel Flynn [2009-07-13 08:31]: > glabel will warn if the last sector is not empty. Does it also shrink the (now) underlying fs? Or is it just a matter of time until the label is overwritten when the fs gets full? If it's an UFS partition, using an UFS volume label is an alternative solution. It also requires you to unmount the partition, but can simply be set on an existing fs with tunefs. > By definition, new installs are not affected by upgrade surprises. The > surprise here that sliceless disks, have their 's1' dropped when upgrading > from 7 to 8.x and using labels would eliminate this surprise and any future > change in disk naming conventions. If I'd have to install a system today, I'd probably install 7.2-R, and it would get upgraded to 8.x-R at some point in the future. Regarding the issue at hand, a current install with sysinstall will not use DDD AFAIK, so it will not run into this particular problem. Alson