From owner-freebsd-questions@freebsd.org Sun Oct 16 19:37:24 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3EAFC1234A for ; Sun, 16 Oct 2016 19:37:24 +0000 (UTC) (envelope-from jasoncwells@fastmail.com) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89B4E1D84 for ; Sun, 16 Oct 2016 19:37:24 +0000 (UTC) (envelope-from jasoncwells@fastmail.com) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A93FD205BF for ; Sun, 16 Oct 2016 15:37:22 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 16 Oct 2016 15:37:22 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=MfXPeEnVOrRQcz+UZ6GuEkFCmkI=; b=RKeXEg LqnmHoCtfRx5KSFyXDFXXcLP/yTQicbMPXnQ256yS/nMIzAbbjO68pwjnJ4iBsdQ v3k5JHzHUHJp5mVeCI6pIGcxVxxfYdlb1CXC5LS/KAXjQDA/12Pv1DZMLydVD0Wo xA3RLMwoBxBwpKRb83ZL9kHAVUQ2CyJtfstVQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:x-sasl-enc:x-sasl-enc; s=smtpout; bh=MfXPeEnVOrRQcz+UZ6 GuEkFCmkI=; b=EaWZTaQLYW/GOZrirwJ6fVIJS/3yUVSilDYl0I96Fk1catoBVL H6DpbYcFtcxSr9WL9ZVRBkgmQa3DVbi+PKazwCSFEqSob9B9ugk+Ca4buBXLT8vX nyoGddj8R7Q4wbwBjlRyDnvvqb6a5Q+lWkxuEyb0b+QitEIde+xh4hB8g= X-Sasl-enc: PAaNibvIDo1SwhxuyZinimYTz4fikOZkVtvPI2SnIdEq 1476646642 Received: from [192.168.1.195] (174-31-141-127.tukw.qwest.net [174.31.141.127]) by mail.messagingengine.com (Postfix) with ESMTPA id 43A1DF29CE for ; Sun, 16 Oct 2016 15:37:22 -0400 (EDT) Subject: Re: Filesystem Label Ambiguity References: <86pon1dwze.fsf@WorkBox.Home> <86y41o8gf8.fsf@WorkBox.Home> Cc: freebsd-questions@freebsd.org From: "Jason C. Wells" Message-ID: Date: Sun, 16 Oct 2016 12:37:21 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <86y41o8gf8.fsf@WorkBox.Home> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 19:37:24 -0000 Thanks guys. I've got it all sorted out now. I've added a physical disk identifier (dN) and a system identifier (sN) to my volume names. Now if I do what I did these past couple days (mixing and matching disks from various systems during a hardware and software upgrade) it will be much easier to unambiguously identify volumes. Regards, Jason C. Wells