Hello Erik, Monday, June 16, 2008, 9:45:13 AM, you wrote:
ET> One thing I should mention on this is that I've had _very_ bad ET> experience with using single-LUN ZFS filesystems over FC. ET> that is, using an external SAN box to create a single LUN, export that ET> LUN to a FC-connected host, then creating a pool as follows: ET> zpool create tank <LUN_ID> ET> It works fine, up until something bad happens to the array, or the FC ET> connection (like, say, losing power to the whole system), and the host ET> computer cannot talk to the LUN. ET> This will corrupt the zpool permanently, and there is no way to fix the ET> pool (and, without some magic in /etc/system , will leave the host in a ET> permanent kernel panic loop). This is a known bug, and the fix isn't ET> looking to be available anytime soon. ET> This problem doesn't seem to manifest itself if the zpool has redundant ET> members, even if they are on the same array (and thus, the host loses ET> contact with both LUNs at the same time). ET> So, for FC or iSCSI targets, I would HIGHLY recommend that ZFS _ALWAYS_ ET> be configured in a redundant setup. Have you got more details or at least bug ids? Is it only (I dboubt) fc related? -- Best regards, Robert mailto:[EMAIL PROTECTED] http://milek.blogspot.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
