Hello, I have a problem after accessing a zpool containing a boot environment from another system. When the zpool is accessed (imported, mounted and exported again) by another system, the device addresses stored in its metadata are overwritten. Consequently, it is not bootable any more and causes a kernel panic when booted. The only solution is to boot from a live CD and do a zpool import/export in exactly the same hardware environment, so that the correct device addresses are restored again.
Can this be avoided? I need the zpool to be both directly bootable and accessible from another (virtual) machine. How can a zpool be imported and mounted without changing the device addresses stored in its metadata? I know those hardware characteristics could be important in RAIDZ scenarios, but this is just one partition... Andrej
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
