From owner-freebsd-stable@FreeBSD.ORG Fri Sep 17 19:06:45 2010 Return-Path: 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 5295810656A3 for ; Fri, 17 Sep 2010 19:06:45 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from mx7.ksu.ru (honey.ksu.ru [193.232.252.54]) by mx1.freebsd.org (Postfix) with ESMTP id 558EB8FC15 for ; Fri, 17 Sep 2010 19:06:43 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.56,384,1280692800"; d="p7s'?scan'208";a="978079" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iport2.ksu.ru with ESMTP; 17 Sep 2010 23:06:30 +0400 X-Pass-Through: Kazan State University Network Received: from zealot.ksu.ru ([194.85.245.161]) by ksu.ru (8.13.4/8.13.4) with ESMTP id o8HJ6AO5023596; Fri, 17 Sep 2010 19:06:10 GMT Received: from zealot.ksu.ru (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.14.4/8.14.4) with ESMTP id o8HJ5cQ8039248; Fri, 17 Sep 2010 23:05:38 +0400 (MSD) (envelope-from amarat@ksu.ru) Message-ID: <4C93BC00.3050707@ksu.ru> Date: Fri, 17 Sep 2010 23:05:36 +0400 From: "Marat N.Afanasyev" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100724 Firefox/3.0.7 MIME-Version: 1.0 To: Michael Sperber References: <201009171238.o8HCcwCl084727@lurza.secnetix.de> <4C93674B.20300@ksu.ru> <4C937933.4060707@ksu.ru> In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010403060804010204060307" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Sep 2010 19:06:45 -0000 This is a cryptographically signed message in MIME format. --------------ms010403060804010204060307 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: quoted-printable Michael Sperber wrote: > "Marat N.Afanasyev" writes: > >> you may try the following commands: >> >> sysctl kern.geom.debugflags=3D16 >> >> foreach fs (your-filesystems) >> glabel label your-$fs-label your-$fs-device >> end >> >> echo geom_label_load=3D"YES">> /boot/loader.conf >> reboot >> >> and see if the labels appear in /dev/label > > Is this safe to do? The man page for glabel seems to imply that glabel= > should be used before newfs, and tunefs after newfs. > probably safe, but I didn't try this. there's another option: you may=20 consider to create gmirror device that allows you to shoot two ducks=20 with one arrow: 1) make your system fail-safe 2) all your devices will=20 be in form /dev/mirror/devXsYl regardless of underlying adX-s. to do=20 this all you need is a second hard drive large enough to serve as copy=20 of your boot drive --=20 SY, Marat --------------ms010403060804010204060307--