From owner-freebsd-stable@FreeBSD.ORG  Fri Sep 17 15:54:18 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9AE131065679
	for <freebsd-stable@freebsd.org>; Fri, 17 Sep 2010 15:54:18 +0000 (UTC)
	(envelope-from milu@dat.pl)
Received: from jab.dat.pl (dat.pl [80.51.155.34])
	by mx1.freebsd.org (Postfix) with ESMTP id E8A0A8FC0A
	for <freebsd-stable@freebsd.org>; Fri, 17 Sep 2010 15:54:17 +0000 (UTC)
Received: from jab.dat.pl (jsrv.dat.pl [127.0.0.1])
	by jab.dat.pl (Postfix) with ESMTP id AD39876;
	Fri, 17 Sep 2010 17:38:04 +0200 (CEST)
X-Virus-Scanned: amavisd-new at dat.pl
Received: from jab.dat.pl ([127.0.0.1])
	by jab.dat.pl (jab.dat.pl [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id kW9OGrQgazGn; Fri, 17 Sep 2010 17:38:01 +0200 (CEST)
Received: from snifi.localnet (unknown [212.69.68.42])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by jab.dat.pl (Postfix) with ESMTPSA id 2BDD867;
	Fri, 17 Sep 2010 17:38:01 +0200 (CEST)
From: Maciej Milewski <milu@dat.pl>
To: freebsd-stable@freebsd.org
Date: Fri, 17 Sep 2010 17:37:58 +0200
User-Agent: KMail/1.13.5 (Linux/2.6.35-ARCH; KDE/4.5.1; x86_64; ; )
References: <201009171238.o8HCcwCl084727@lurza.secnetix.de>
	<4C937933.4060707@ksu.ru> <y9laang77zr.fsf@deinprogramm.de>
In-Reply-To: <y9laang77zr.fsf@deinprogramm.de>
X-KMail-Markup: true
MIME-Version: 1.0
Message-Id: <201009171738.00057.milu@dat.pl>
Content-Type: text/plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: "Marat N.Afanasyev" <amarat@ksu.ru>,
	Michael Sperber <sperber@deinprogramm.de>
Subject: Re: How to predict drive number change for 7.3->8.1 upgrade?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 15:54:18 -0000

Dnia pi=B1tek 17 wrzesie=F1 2010 o 16:35:52 Michael Sperber napisa=B3(a):
> "Marat N.Afanasyev" <amarat@ksu.ru> writes:
> > you may try the following commands:
> >=20
> > sysctl kern.geom.debugflags=3D16
> >=20
> > foreach fs (your-filesystems)
> > glabel label your-$fs-label your-$fs-device
> > end
> >=20
> > echo geom_label_load=3D"YES" >> /boot/loader.conf
> > reboot
> >=20
> > and see if the labels appear in /dev/label
>=20
> Is this safe to do?  The man page for glabel seems to imply that glabel
> should be used before newfs, and tunefs after newfs.
It's because geom class uses the last sector of the provider to keep his=20
metadata, so if you will overwrite this sector then you lose this metadata(=
in=20
this case label). So to not lose this metadata you should use geom_label fi=
rst=20
and then newfs on the /dev/label/...
I think that using ufs label should be sufficient, glabel supports them too=
=20
(under /dev/ufs directory).

Maciek