Date: Fri, 10 Jul 2009 21:39:05 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Marcel Moolenaar <xcllnt@mac.com> Cc: freebsd-geom@freebsd.org Subject: Re: glabel and real disk IDs Message-ID: <20090710193905.GA1463@garage.freebsd.pl> In-Reply-To: <0903FECF-3D0D-430E-9E93-C6DC00CA1BC5@mac.com> References: <h34lml$6fv$1@ger.gmane.org> <20090709200102.GA2438@garage.freebsd.pl> <C3B56501-1F02-42FC-B848-DD3969965E82@mac.com> <20090709222420.GE2438@garage.freebsd.pl> <0903FECF-3D0D-430E-9E93-C6DC00CA1BC5@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 10, 2009 at 09:37:30AM -0700, Marcel Moolenaar wrote: >=20 > On Jul 9, 2009, at 3:24 PM, Pawel Jakub Dawidek wrote: > >>I see ZFS getting confused when disks are shuffled around. > >>The confusion is the result of having device paths stored > >>in the ZFS label match the device name of some other vdev > >>that part of the same pool. > >> > >>Replacing a device with itself doesn't help, because ZFS > >>complains that the vdev is part of an active pool in that > >>case. It seems that only labels will work here... > > > >Solaris is using device names stored in ZFS label and if this is not =20 > >the > >drive it was looking for, it is doing ID-to-path translation to find =20 > >new > >path name. On FreeBSD on the other hand (after upgrade to v13) I =20 > >gave up > >doing similar thing because disk IDs weren't available from all disk > >device drivers (I implemented it for ATA and I received no help with > >other drivers). Currently the idea is to just go through all GEOM > >providers looking for proper ZFS metadata (think of it as manual > >tasting), so even if device name changes, ZFS should be able to locate > >it. If there are still problems locating the disk, there simply =20 > >might be > >a bug in the code of some sort. >=20 > Disks are found correctly, it's just that ZFS' internal > state is messed up. It uses both the device special file > name and the stored vdev path and as such can end up with > multiple VDEVs of the same name. As such, some VDEVs are > marked as corrupted/faulted. >=20 > I can reproduce it if you're interested. I am, but I'm leaving tomorrow and I'll be out of e-mail probably for the next two weeks. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKV5jZForvXbEpPzQRAr03AJsF921Ea0XXYQCq9gCcoyD+AD/9RACfUfgI 81nNqiHAL+q5drV81T47IZ0= =s6SN -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090710193905.GA1463>