Hey Miles, Yes, you remembered right. If the zpool.cache file is there, Solaris will mount the pool fine on boot with or without the slog. So if you're running a slog, make sure you keep a backup of that file! I was told that work is being done to make zpool import work the same way so pools with missing slogs can be imported, but that's not available yet so this is definately a bit of a problem for now.
However, I also found that once you have the pool online, you can happily replace the missing slog with another device. In my case, I didn't have an iRAM available, so I was using a regular ramdisk as my slog device to see what effect it had on performance for us. To get it working after a reboot, I just wrote a boot script that creates a new ramdisk with the same name, and adds it to the pool with zpool replace. Obviously that's not for production use, but it was an interesting test, just a 256MB slog gave us an immediate 12x performance boost over NFS. Ross -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
