Jack Dumson wrote: > Issues with ZFS and Sun Cluster > > If a cluster node crashes and HAStoragePlus resource group containing ZFS > structure (ie. Zpool) is transitioned to a surviving node, the zpool > import can cause the surviving node to panic. Zpool was obviously not > exported in controlled fashion because of hard crash. Storage structure > is - HW RAID protected LUN from array. Zpool build on single HW LUN.
You've got no redundancy from a ZFS perspective. > Zpool created on a full device (zpool create HAzpool c1t8d0s2). No RAID-Z > configured. > > I was under the impression that ZFS was always maintained in a > perpetually consistent state. It's a *lot* easier for ZFS to achieve this if you provide it with a redundant configuration for it to manage. > Panic of surving node appears to be related > to some form of silent corruption in ZFS. But I thought the whole design > of ZFS was to prevent this very thing. Is RAID-Z required to achieve this > resiliency? Again, redundancy from ZFS' perspective. > ZFS is officially supported under Sun Cluster but this situation concerns > me greatly because the whole purpose of a cluster is undermined if a > single resource group using HA ZFS causes a panic on import. The effect > could bring the whole cluster down. > Has anyone got any thoughts, comments or similar experiences on this. I'm pretty sure that the Cluster configuration guide will have spelt out the ZFS requirements. Apart from that, please look at the ZFS Best Practices site http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
