I'm not certain if I'm misunderstanding you- or if you didn't read my post carefully.
Why would the zpool.cache file be current on the _second_ node? The first node is where I've added my zpools and so on. The second node isn't going to have an updated cache file until I export the zpool from the first system and import it to the second system no? In my case- I believe both nodes have exactly the same view of the disks- all the controllers and targets are identical- but there is no reason they have to be as far as I know. As such- simply backing up the primary systems zpool.cache to the secondary could cause problems. I'm simply curious if there is a way for a node to keep it's zpool.cache up to date without actually importing the zpool. i.e. is there a scandisks command that can scan for a zpool without importing it. Am I misunderstanding something here? -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss