One thing I should mention on this is that I've had _very_ bad experience with using single-LUN ZFS filesystems over FC.
that is, using an external SAN box to create a single LUN, export that LUN to a FC-connected host, then creating a pool as follows: zpool create tank <LUN_ID> It works fine, up until something bad happens to the array, or the FC connection (like, say, losing power to the whole system), and the host computer cannot talk to the LUN. This will corrupt the zpool permanently, and there is no way to fix the pool (and, without some magic in /etc/system , will leave the host in a permanent kernel panic loop). This is a known bug, and the fix isn't looking to be available anytime soon. This problem doesn't seem to manifest itself if the zpool has redundant members, even if they are on the same array (and thus, the host loses contact with both LUNs at the same time). So, for FC or iSCSI targets, I would HIGHLY recommend that ZFS _ALWAYS_ be configured in a redundant setup. -- Erik Trimble Java System Support Mailstop: usca22-123 Phone: x17195 Santa Clara, CA Timezone: US/Pacific (GMT-0800) _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
