From owner-freebsd-hackers@freebsd.org Mon Feb 27 01:28:12 2017 Return-Path: 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 1AA59CEFDC0 for ; Mon, 27 Feb 2017 01:28:12 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A4C2A8CA for ; Mon, 27 Feb 2017 01:28:11 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id v77so50540966wmv.1 for ; Sun, 26 Feb 2017 17:28:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HrUqgAWlvpO4Y0oIsecCLSylswHE8uj7UAM+Wroe+JM=; b=oKPhVgkAUlR5lvTHSToIU5hl23NrZavu1g1+wpppTfNCaDg7IgYkIJdLYr61jMBoyx MCNJDip5M9B12cx/fBU2Z1SXEYvs1y4p5WVpCbCfWEiBXZ74J80SfSoM6HfluQ9RHZJa CI6WOCCvFjI8JWNh+4xL/zxNi7Sm4LlAoOsQKX2dHGpGeT2KqmoSbTBkTxErp0SjLESx KTGUutl7UHHbeDnbcv2wLGxHGK/CSroPfiPRQIz1C/mZRe3HO0g+VNNDsx51GBM1CYpa LT34IDFngM3FLWnh6AprRE5wzGPn2qM13ep4nK0Y/reJpiNJgmnqbXY73Qm1pYbn29zJ 3qKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HrUqgAWlvpO4Y0oIsecCLSylswHE8uj7UAM+Wroe+JM=; b=VMjQCQ7mzidhmoVQh5TrAr4yzu/dj31OYvVmZTUsb0s2aeg0tQfaH+GkFOyJK1IKA+ wX3kuINS2bSRofmx5ETRcn/EXWPRz9I7zf6z5SMy2JEQ84L4jjbbCXN+q6sAjeLsRudq rinPX40py+3tViKY0LX5vEaPPaTc8d7GVvvBn3dhx4d9M/B2OTIKcSFaNcAtWEgdeZWy J31rzkhiGOBfWOHpE0EEJGEpVN2DwGlRa7HORtvk4JatleFqjWIIdJsPPZNMkYbOM384 tgfAm5MPvb4Dfbnc5eSjMO4pELBkYz8wJIPcgrxI/qYiwb3Bu9aSkRaTdig9iHNY8gko LyYQ== X-Gm-Message-State: AMke39lbrnHTwEHcPCd9EC/Yv0f9gRB++U0wDrAew3aF5HJkyoXldZCnnhYnE+CpbW38plA5hrTcrwfg8oLhSg== X-Received: by 10.28.10.70 with SMTP id 67mr11667496wmk.76.1488158888982; Sun, 26 Feb 2017 17:28:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.158.102 with HTTP; Sun, 26 Feb 2017 17:28:08 -0800 (PST) In-Reply-To: References: From: Zaphod Beeblebrox Date: Sun, 26 Feb 2017 20:28:08 -0500 Message-ID: Subject: Re: ZFS should prefer the most specific... or something. To: Andrey Fesenko Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2017 01:28:12 -0000 On Sun, Feb 26, 2017 at 7:09 PM, Andrey Fesenko 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.