should zfs care so much about device name changes

[Nikolay Denev]

On 27 Feb, 2010, at 22:47 , Pawel Jakub Dawidek wrote:

> On Wed, Feb 24, 2010 at 03:58:58PM +0200, Nikolay Denev wrote:
>> 
>> On Feb 24, 2010, at 11:53 AM, Nikolay Denev wrote:
>> 
>>> Hello,
>>> 
>>> 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? 
>>> 
>>> 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?
>>> 
>>> 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?
> 
> Try adding vfs.zfs.debug=1 to /boot/loader.conf. This will hopefully
> show what's going on.
> 
> -- 
> Pawel Jakub Dawidek                       http://www.wheel.pl
> pjd at FreeBSD.org                           http://www.FreeBSD.org
> FreeBSD committer                         Am I Evil? Yes, I Am!

Sorry for the noise, it seems like it's not zfs's fault, the machine just doesn't see
any disks because I added ATA_CAM but missed atacore and atapci.
I had to capture the boot screen with my camera because my USB keyboard does not
work on rootfs mount prompt and I was not able scroll up to see what's the cause,
but that's another problem that deserves another thread not in -fs.

Thanks,
Niki