On Fri, Dec 15, 2006 at 08:11:08PM +0000, Ricardo Correia wrote: > With the help of dtrace, I found out that in vdev_disk_open() (in > vdev_disk.c), the ddi_devid_compare() function was failing. > > I don't know why the devid has changed, but simply doing zpool export ; > zpool > import did the trick - the pool imported correctly and the contents seem to > be intact. > > Examining the backup logs, I can see some rather strange behaviour on the > part > of ZFS during the rsync! I'm not even going to try to understand it, but I'm > keeping the logs if anyone is interested.
Ah, you're running into this bug: 650054 ZFS fails to see the disk if devid of the disk changes due to driver upgrade Basically, if we have the correct path but the wrong devid, we bail out of vdev_disk_open(). But what we really should do is trust the path, and then let the higher level code (vdev_validate()) make sure it's still the right device. This should be fixed soon, as we need it to handle some upcoming devid changes. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
