From owner-freebsd-questions@freebsd.org Wed Sep 23 21:34:39 2015 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 BB380A0721A for ; Wed, 23 Sep 2015 21:34:39 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com [209.85.220.181]) (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 780661A5F for ; Wed, 23 Sep 2015 21:34:38 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qkdw123 with SMTP id w123so22860515qkd.0 for ; Wed, 23 Sep 2015 14:34:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=iauLD8CfSbLO+YxCUBCUS5WGUG2HMBzKg62Dno0rK58=; b=A/NFRms+IDgWQnXsNMSXPdSlGD49KL9ZcEfDz2l2pepvMSrWqf4H/uzAQTP5rLZ8CY jwBaQN80fzX0o6Y6foHMNRRGl3mnxTkTcyKpLWC1Xgvnd0DlxD/zjAIczQfVsHlgMN4X GanM9oLY4hdAedlDcGilOP+EkkAATyxkYoIXvjqLXEfjIH38TZzCb9YrtzTrXG99rBFY RDbd6Tzddswl/XF8PVUpWOLVedIy0RNTh4ys9RSlPOJpTSOy2FhqQks3cve36oQRsYlQ unKXwiPCzguVo7lDeeFeUQUtYrTtVl7eaElBcMG/8fhvJdSzNQJb6pp6CLO5K9jVhDg6 /Vaw== X-Gm-Message-State: ALoCoQlOw3PxLZUDOLUR3lpNCgTbVCdj+DZhbK79oGQ1h9keDTxHVF0txi1tRWQNlkx59HM+95t/ X-Received: by 10.55.54.75 with SMTP id d72mr39547735qka.52.1443042422207; Wed, 23 Sep 2015 14:07:02 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by smtp.gmail.com with ESMTPSA id s89sm3239831qks.36.2015.09.23.14.07.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Sep 2015 14:07:00 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Name/label/id metadata: how do I make it go away From: Paul Kraus In-Reply-To: <5603114C.2060105@stankevitz.com> Date: Wed, 23 Sep 2015 17:06:55 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <56004C68.4020904@stankevitz.com> <5600F0DF.8000805@stankevitz.com> <5601A82A.7040304@stankevitz.com> <5601B2AF.7040306@stankevitz.com> <5601CB85.8070400@stankevitz.com> <93BD5F1D-9A64-4430-8519-FCF71E817A29@kraus-haus.org> <5603114C.2060105@stankevitz.com> To: Chris Stankevitz , FreeBSD Questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 21:34:39 -0000 On Sep 23, 2015, at 16:53, Chris Stankevitz = wrote: > I feel the same way about my data. Like you, I am paranoid and I want = to understand exactly what is going on. How can I guarantee that my = data is safe when I'm at a loss to explain why my "zpool status" is such = a mess? >=20 > Can you tell me how you go about "preferring and using diskids" when = you import a zpool? Do you always import on the command line using = "zpool import -d=94? I create the zpool using the /dev/diskid/nnn device names. If I build = the zpool using those device names I have not had ZFS use any others on = import. When I have a zpool that does not use the diskid device names I usually = (and very carefully) replace the device with one using the diskid name. = You clearly can=92t do that =93in-place=94 with RAIDz vdevs, but for = mirrors I take the small risk by removing one of the mirror components = and then attach it using the diskid name. If you have even one =93spare=94 drive you can do a walking replacement = of one device at a time to the new naming scheme. I have not run into the exact case you have with device names but no = idea (really) where they came from. If your zpool started under FreeNAS, then you need to be looking at how = 9.x handles device names to figure out where they came from. As far as I = know, FreeNAS is still 9.x based. NOTE: I am running 10.0 and 10.1, I have not gone to 10.2 yet. -- Paul Kraus paul@kraus-haus.org