Date: Thu, 26 Nov 2009 18:10:10 +0700 From: Edho P Arief <edhoprima@gmail.com> To: Scot Hetzel <swhetzel@gmail.com> Cc: freebsd-stable@freebsd.org, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: Can't use gpt labels re-importing pool Message-ID: <a3780c060911260310m4974f809oe2370e716b60f663@mail.gmail.com> In-Reply-To: <790a9fff0911260229u40d9f499w28a7ce46e1f92467@mail.gmail.com> References: <4B0E3ABA.3030606@tzim.net> <790a9fff0911260040i1456d7c0j4f8327d24d2966cf@mail.gmail.com> <20091126085034.GA51998@icarus.home.lan> <790a9fff0911260229u40d9f499w28a7ce46e1f92467@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 26, 2009 at 5:29 PM, Scot Hetzel <swhetzel@gmail.com> wrote: > On 11/26/09, Jeremy Chadwick <freebsd@jdc.parodius.com> wrote: >> I'm a bit curious about something, so maybe someone can help me >> =C2=A0understand: >> >> =C2=A0Why are people bothering with GPT labels (or in some cases, glabel= s) >> =C2=A0when AHCI (whether it be ataahci.ko or ahci.ko) is in use? =C2=A0U= nder what >> =C2=A0circumstance would the device name change dynamically in this situ= ation? >> > > There was a thread about this problem where the drives had changed > their device names due to a change in the kernel drive =C2=A0(Current lis= t > from July): > > http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009377.html > > Through out this thread there were various suggests on how he could > recover the system, and prevent the problem from occurring in the > future. > > One of the suggestions was that use of zpool replace to change from > device names to using glabel labels. > > http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009440.html > >> =C2=A0I've never witnessed this happening with AHCI, at least on Intel >> =C2=A0systems, and I've hot-swapped hard disks many times over. >> > > Using glabels, gpt labels, or gptid solves the problem of not needing > to remember which device name the drive originally had. =C2=A0For instanc= e, > on a zfs zraid pool with 3 disks (ad1 ad2 ad3) you could disconnect > the pool from one computer and connect it to another system and it > wouldn't matter which order you reconnected the drives (1 2 3 or 3 =C2=A0= 1 > 2) as the pool would still be recognized when it is imported on the > new system. =C2=A0Also if the new system already has drives ad1 and ad2, = it > wouldn't matter. > > Scot for some reasons it sounds to me like 'avoiding problem' since device name shouldn't matter in zfs (or so I read) --=20 O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a3780c060911260310m4974f809oe2370e716b60f663>