Date: Wed, 23 Sep 2015 13:53:32 -0700 From: Chris Stankevitz <chris@stankevitz.com> To: Paul Kraus <paul@kraus-haus.org>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Name/label/id metadata: how do I make it go away Message-ID: <5603114C.2060105@stankevitz.com> In-Reply-To: <93BD5F1D-9A64-4430-8519-FCF71E817A29@kraus-haus.org> References: <56004C68.4020904@stankevitz.com> <alpine.BSF.2.20.1509212126470.4544@wonkity.com> <5600F0DF.8000805@stankevitz.com> <e1abb521ab324532b3445d26984f5638@SERVER.ad.usd-group.com> <5601A82A.7040304@stankevitz.com> <5601B2AF.7040306@stankevitz.com> <alpine.BSF.2.20.1509221500580.14674@wonkity.com> <5601CB85.8070400@stankevitz.com> <93BD5F1D-9A64-4430-8519-FCF71E817A29@kraus-haus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/23/15 10:07 AM, Paul Kraus wrote: > I actually prefer the /dev/diskid/nnn names as those are tied to the > physical drives. By using them I guarantee that even if a drive > physically (or logically if drives or controllers are added) moves > the system can still find and import the zpool. In the early days of > ZFS one of the best ways to damage a zpool was to rearrange drives so > that the ZFS label (and cache) no longer agreed with reality. I was > in the habit of manually exporting critical zpools before making any > hardware changes and after the changes were complete I would import > the pool (sometime with new device names). ZFS _should_ be robust > enough to handle device movement today, but I am slightly paranoid > when it comes to critical data. Paul, 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? 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"? Thank you, Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5603114C.2060105>