From owner-freebsd-questions@freebsd.org Sat Oct 15 23:35:34 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 27C43C13393 for ; Sat, 15 Oct 2016 23:35:34 +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 F2C06E55 for ; Sat, 15 Oct 2016 23:35:33 +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 DF83020685; Sat, 15 Oct 2016 19:35:32 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Sat, 15 Oct 2016 19:35:32 -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:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=kYffSrDCFnCz7BHivo0HtPe2YJA=; b=dmby5R cbMME/Ced4tdGyDNKllibxK1f7YRQnz82Wh9vNxuPKyyjB1hyVOeCBe0LVemx1Wv m3L7tfiRhmsHR3hvwYGAAWmkJf3IfIR5GrMTgIxpK4B2/bt/1/ls86xwXf5Hc0xr /f6c8BdjMpzJOx55U1Gjgd1tH+24KzWWC8vmU= 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:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=kYffSrDCFnCz7BH ivo0HtPe2YJA=; b=q/SFDFSrht6oFWGAk627Wupfrzr6TnMJVXBvLFXztUObanR pUzxmP9ZeRnkbyCllDX2D0ZnqADOoOlMowW0KPDRLBKT5jC8QhFRGui9umlkzsN3 hWPHpEZOuu8eKqSMmikjv8pZKN8r5Y6Looe4uxDyOSwJC9h67foq2zI1f9v0= X-Sasl-enc: VWBMiYIkrfu7cHnPbH0nE+Hwl52iludFCf4hdVrfGAwq 1476574532 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 669D5CC0B6; Sat, 15 Oct 2016 19:35:32 -0400 (EDT) Subject: Re: Filesystem Label Ambiguity To: "Brandon J. Wandersee" References: <86pon1dwze.fsf@WorkBox.Home> Cc: freebsd-questions@freebsd.org From: "Jason C. Wells" Message-ID: Date: Sat, 15 Oct 2016 16:35:31 -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: <86pon1dwze.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: Sat, 15 Oct 2016 23:35:34 -0000 On 10/15/2016 4:16 PM, Brandon J. Wandersee wrote: > Jason C. Wells writes: > >> Let's say I have three disks and each of them has a partition labelled >> "volume3" i.e. /dev/ufs/volume3. >> >> How can I determine which of those is currently mounted? >> >> How does the system determine which of those to mount at boot time? > Short answer: Don't do this. OK. So the device renumbering problem has been traded for a naming ambiguity problem. I didn't realize this when I first came upon my naming convention for filesystems. I'll start keeping track of my "volumeX" names and make them unique. I just got lucky that I didn't mount the wrong disks over the course of the last few weeks. Maybe I'll just use UUIDs everywhere. Those are easy to remember. :) Thanks, Jason C. Wells