Date: Thu, 26 Nov 2009 15:07:40 +0200 From: Nikolay Denev <ndenev@gmail.com> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: Can't use gpt labels re-importing pool Message-ID: <27DF657E-A14A-4B6F-ABE5-877B018FEE42@gmail.com> In-Reply-To: <helqdu$uui$1@ger.gmane.org> References: <4B0E3ABA.3030606@tzim.net> <790a9fff0911260040i1456d7c0j4f8327d24d2966cf@mail.gmail.com> <20091126085034.GA51998@icarus.home.lan> <helqdu$uui$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 26, 2009, at 1:56 PM, Ivan Voras wrote: > Jeremy Chadwick wrote: >=20 >> Why are people bothering with GPT labels (or in some cases, glabels) >> when AHCI (whether it be ataahci.ko or ahci.ko) is in use? Under = what >> circumstance would the device name change dynamically in this = situation? >> I've never witnessed this happening with AHCI, at least on Intel >> systems, and I've hot-swapped hard disks many times over. >=20 > It isn't specific to AHCI, but this is where most people encountered = it first. The issue in question is "how to make ZFS survive drive = renaming" for any cause - driver change, controller change, drive = shuffling, etc. >=20 > In general, ZFS will taste individual drives on "zpool import" so will = try to do the right thing, but it might pick up different labels for = different drives, etc. Using glabel tricks simply makes the naming a bit = more consistent. >=20 >=20 What about "zpool import -d /dev/gpt/" ? Though last time I tried this it refused to work for some reason.=20 Regards, Niki Denev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27DF657E-A14A-4B6F-ABE5-877B018FEE42>