From owner-freebsd-hackers@freebsd.org  Mon Feb 27 11:58:56 2017
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@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 7CCE3CEFE96
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Mon, 27 Feb 2017 11:58:56 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (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 3E406C26
 for <freebsd-hackers@freebsd.org>; Mon, 27 Feb 2017 11:58:56 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1ciJx8-000JdQ-2w; Mon, 27 Feb 2017 14:58:54 +0300
Date: Mon, 27 Feb 2017 14:58:54 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Zaphod Beeblebrox <zbeeble@gmail.com>
Cc: Andrey Fesenko <f0andrey@gmail.com>,
 FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject: Re: ZFS should prefer the most specific... or something.
Message-ID: <20170227115854.GK15630@zxy.spb.ru>
References: <CACpH0Meg5MjOGCohSMrAdwdRG_smVNY6CNVRaUSXw9cq0x2YsA@mail.gmail.com>
 <CA+K5SrP=p7xqFOjPM4BvDuyitM951biu8ZNoKuin8A_TfeG1xQ@mail.gmail.com>
 <CACpH0MdQKuHD9XNRh=VYa6nHh5YpQnpa-yjmHyk08j7mZUEg1g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACpH0MdQKuHD9XNRh=VYa6nHh5YpQnpa-yjmHyk08j7mZUEg1g@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 11:58:56 -0000

On Sun, Feb 26, 2017 at 08:28:08PM -0500, Zaphod Beeblebrox wrote:

> On Sun, Feb 26, 2017 at 7:09 PM, Andrey Fesenko <f0andrey@gmail.com> wrote:
> 
> >
> > "A disk can be specified by a full path to the device or the geom(4)
> > provider name" see zpool(8)
> > For example gpt lables
> >
> >
> Yeah,  no.  You didn't read carefully.  Let me be more clear.  Some random
> rejig of device names causes zfs to abandon your carefully constructed
> name.  GPT and GPT labels are more stable, but some machines will not allow
> a GPT label.  Anyways, after the random event, you have maximally long,
> low-signal-to-noise ratio names.

zfs don't need label, zfs can use raw disk name and full tolerante to
change this names between reboot.

ps: /boot/loader.conf:

kern.geom.label.gptid.enable="0"
kern.geom.label.disk_ident.enable=0