From owner-freebsd-questions@freebsd.org Tue Jun 13 22:03:36 2017 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 73CD2BFF5E9 for ; Tue, 13 Jun 2017 22:03:36 +0000 (UTC) (envelope-from freebsd-doc@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1DB876ACC7 for ; Tue, 13 Jun 2017 22:03:35 +0000 (UTC) (envelope-from freebsd-doc@fjl.co.uk) Received: from [192.168.1.35] (host86-191-88-133.range86-191.btcentralplus.com [86.191.88.133]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id v5DLqtVR093160 for ; Tue, 13 Jun 2017 22:52:55 +0100 (BST) (envelope-from freebsd-doc@fjl.co.uk) To: freebsd-questions@freebsd.org From: Frank Leonhardt Subject: Drive labelling with ZFS Message-ID: <03643051-38e8-87ef-64ee-5284e2567cb8@fjl.co.uk> Date: Tue, 13 Jun 2017 22:52:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Tue, 13 Jun 2017 22:03:36 -0000 Can anyone help me? I'm going quietly crazy here with FreeBSD 11-RELEASE If you're creating a non-trivial ZFS raidz zpool, I've heard it said that labelling the GPT partitioned drives with their shelf and row number is A Good Thing. (I'm not talking about sticky labels stuck on the drive, but they're good too). When you look at a healthy zpool status you get a list of all the GEOMs, but when one fails it's identified by the GUID and not the device. Good luck tracking it down from that piece of information, unless it's also making a strange buzzing noise. So I though I'd just use use glabel label to set a label on the vdev (e.g "/dev/da7p3") and zpool would use that instead. Nope; only the GUID. I also, naively, thought that setting the label would cause it to appear as a device in /dev/gpt/ What have I not understood? I have a theory - label the partitions before creating the zpool, and add them to the zpool afterwas by a /dev/gpt/ name. Except I have lost confidence that the label would appear in /dev/gpt/. It could be that /dev/gpt names don't appear if they're part of a zpool. However, testing this theory is going to involve hassle (i.e. the destruction and rebuilding of the entire zpool) so if anyone could tell me if I'm heading in the right direction I'd appreciate it. I may well have missed something trivial here. Thanks, Frank.