On 12/10/06, Ceri Davies <[EMAIL PROTECTED]> wrote:
On Wed, Oct 11, 2006 at 11:49:48PM -0700, Matthew Ahrens wrote:
> FYI, /etc/zfs/zpool.cache just tells us what pools to open when you boot > up. Everything else (mountpoints, filesystems, etc) is stored in the > pool itself. What happens if the file does not exist? Are the devices searched for metadata?
My understanding (I'll be delighted if I'm wrong) is that you would be stuffed. I'd expect: zpool import -f (see the manpage) to probe /dev/dsk/ and rebuild the zpool.cache file, but my understanding is that this a) doesn't work yet or b) does horrible things to your chances of surviving a reboot [0]. This means that for zfs root and failsafe boots, you need to have a zpool.cache in your boot/miniroot archive (I probably have the terminology wrong) otherwise the boot will fail. I was asking if it was going to be replaced because it would really simplify ZFS root. Dick. [0] going from: http://solaristhings.blogspot.com/2006/06/zfs-root-on-solaris-part-3.html -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/ _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
