From owner-freebsd-questions@FreeBSD.ORG Tue Oct 20 15:31:04 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E42961065670 for ; Tue, 20 Oct 2009 15:31:03 +0000 (UTC) (envelope-from michael.copeland@gmail.com) Received: from mail-qy0-f192.google.com (mail-qy0-f192.google.com [209.85.221.192]) by mx1.freebsd.org (Postfix) with ESMTP id 5A6528FC27 for ; Tue, 20 Oct 2009 15:31:03 +0000 (UTC) Received: by qyk30 with SMTP id 30so4493011qyk.7 for ; Tue, 20 Oct 2009 08:31:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=/RP/2OAgZfxmtJOOqEVecDxn79YN+SJ+BdGVz5zLgQs=; b=PJEonENFhQS7Uc76hjvQppt5yIv0oX8nMzOLdtuBxN5w+JXmMh4z89SuL64xKDSbYh 4J4GGCxtNn6e2B7osyOx/TXWGedxppQFEImWmmUpCEuYW7engLtQkgfml4DyENCKoAHz b1Td28QKv5EcAPcQ4rsykIJGwH52bVQmy2u64= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=O/68sOpT8tcsdaSE+mhQxQZhgumb5X+5wpe6dpghnf0bp0Ek3+dIhIkm1Jwhrou049 rfrpQcmB/SbbvCyi0pJV/AN/o2ZDeyaEcv58PEkgfsDcgEWo3ZyfoEYazkpYfgH+liXr eTRR4Qlu2sf1xbMQ/p1COUNZBddh/Ld5zir1Y= Received: by 10.224.14.81 with SMTP id f17mr3294809qaa.124.1256052662758; Tue, 20 Oct 2009 08:31:02 -0700 (PDT) Received: from ?192.168.1.76? (99-166-165-150.lightspeed.jcvlfl.sbcglobal.net [99.166.165.150]) by mx.google.com with ESMTPS id 22sm4243097qyk.10.2009.10.20.08.30.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Oct 2009 08:31:00 -0700 (PDT) Message-ID: <4ADDD7B6.7030506@gmail.com> Date: Tue, 20 Oct 2009 11:31:02 -0400 From: michael User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Polytropon References: <4ADC6D89.10600@videotron.ca> <57200BF94E69E54880C9BB1AF714BBCBA57086@w2003s01.double-l.local> <4ADC772F.3060303@videotron.ca> <6201873e0910190729v12f66335xe93d0c83a0ee7aee@mail.gmail.com> <4ADC794F.3050505@videotron.ca> <6201873e0910190737o1d849953h6761085ba532f8f6@mail.gmail.com> <4ADC7BD3.30301@videotron.ca> <6201873e0910190809h3cd4416bxaaf526008110447a@mail.gmail.com> <4ADC8C9A.4030903@videotron.ca> <6201873e0910190912w42325e0q541d46bc2a2972fb@mail.gmail.com> <4ADC9DE6.6020900@videotron.ca> <20091020053531.758c5a67.freebsd@edvax.de> <4ADD89A1.9060204@videotron.ca> <20091020124354.85465feb.freebsd@edvax.de> In-Reply-To: <20091020124354.85465feb.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: glabel clarification X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2009 15:31:04 -0000 Polytropon wrote: > On Tue, 20 Oct 2009 05:57:53 -0400, PJ wrote: > >> Exactly what is happening on my system. That's basically what has been >> troubling me. I cloned ad12 to ad6 and then wanted to boot from ad6... >> well, everytime I boot from ad6 the boot is from ad12 because both have >> identical labels. The only way out is to change the labels on ad6 to >> point to ad6 partitions and not to /dev/label/name. >> > > That is a solution for the case that you want to keep both > disks running in the system. If you just want to make one > disk (b) available in order to swap it when the master disk > fails (w), then labels are fine. > > I'm not sure what your main purpose of cloning the disks > was. Two options: > a) keep two disks in sync, so you can use your > backup disk when the working disk fails and > needs to be extracted > b) make a clone of your working disk so it can > be placed into another system > > > > >> So the only reason to use glabel, in my case, is to boot from the clone >> on another system without worrying about the actual disk label. Once >> it's booted, the label can be changed to conform to the label on the new >> system. >> > > The label doesn't need to be changed when the disk in question > is placed into another system. Labels work independent from > the different settings you might find in different computers, > such as different device names (due to different position on > the controller). > > > > LONGEST glabel discussion ever.