Date: Wed, 24 Feb 2010 15:58:58 +0200 From: Nikolay Denev <ndenev@gmail.com> To: freebsd-fs@freebsd.org Subject: Re: should zfs care so much about device name changes Message-ID: <272C3933-72C9-41AF-AD3A-605A7C57FB61@gmail.com> In-Reply-To: <26CCAE99-B056-4754-9324-2945D1643C78@gmail.com> References: <26CCAE99-B056-4754-9324-2945D1643C78@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 24, 2010, at 11:53 AM, Nikolay Denev wrote: > Hello, >=20 > I wanted to test the new option ATA_CAM, but that would require a boot = from another media (USB Drive/CD) and a zpool export/import > to update the vdev names. (actually it's shown as "path" in the = zpool.cache file) because otherwise the system would refuse to = open/mount > the pool. > But is that really necessary given the fact that all the devices are = here, and have matching GUIDS to those in the zpool.cache file? > Shouldnt ZFS just import the pool?=20 >=20 > In the current state what would one have to do to for example test = ATA_CAM on a remote machine, where export/import from a rescue > media is not possible? >=20 > Thanks, > Niki I have now looked at = sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_geom.c and it seems = that when a vdev isn't found by pathname it is being searched by guid. But it doesn't seem to be the case here. The = loader sees the pool and boots the kernel, but then the kernel does not = see the pool. Any ideas? Regards, Niki Denev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?272C3933-72C9-41AF-AD3A-605A7C57FB61>