Folks, I''m trying to figure out whether we should give ZFS / mpxio a shot on one of our research servers, or simply skip it (as we have previously). In Nov 2009 Cindy responded to a thread concerning ZFS device issues, cfgadm, and mpxio: http://mail.opensolaris.org/pipermail/zfs-discuss/2009-November/033496.html I''ve got an x2270 with the Sun EZ-SAS HBA and external SATA JBODs (not J4xxx). The external disks simply provide bulk storage; lousy performance is not a concern, reliability is. For obscure reasons, we''re going to destroy / re-create those pools. We originally skipped mpxio due to the cfgadm issues, even though we''d have preferred to have the reliablity enhancements. Those issues seem to have re-appeared in various guises (e.g. bug 6948701, nominally fixed in s10u9). Due to the need to inter-operate (zfs send) with other s10u7 machines, I don''t think moving to update 9 is an option (yet), nor is OSOL or SXCE. Bottom line: Do ZFS / mpxio / cfgadm issues still make mpxio an iffy proposition as a reliability enhancement? Is there a patch set that addresses ZFS / cfgadm / mpxio issues for s10u7? TIA. Bryan -- Bryan Hodgson Lehigh University Computer Science & Engineering Packard Lab 019 room 115 19 Memorial Drive West Bethlehem, PA 18015-3016
On Fri, November 5, 2010 11:16, Bryan Hodgson wrote: [...]> Do ZFS / mpxio / cfgadm issues still make mpxio an iffy proposition > as a reliability enhancement? > > Is there a patch set that addresses ZFS / cfgadm / mpxio issues for > s10u7?Have you considered using S10u9, but simply create pools with the version that U7 supports? From zpool(1M): zpool create [-fn] [-o property=value] ... [-O file-system- property=value] ... [-m mountpoint] [-R root] pool vdev ... [...] -o property=value [-o property=value] ... Sets the given pool properties. See the "Properties" section for a list of valid properties that can be set. [...] pool version 22 default [This is for U9. -- DM] Later on a "zpool upgrade" can be done: zpool upgrade [-V version] -a | pool ... [...] -V version Upgrade to the specified version. If the -V flag is not specified, the pool is upgraded to the most recent version. This option can only be used to increase the version number, and only up to the most recent version supported by this software.
David Magda pointed out (in a note to me) that version is a property that can be set at pool create time, which solves my question concerning upgrading to s10u9 rather handily. Thank you, David. On Fri, Nov 05, 2010 at 11:16:18AM -0400, Bryan Hodgson wrote:> > Folks, > > I''m trying to figure out whether we should give ZFS / mpxio a shot > on one of our research servers, or simply skip it (as we have > previously). > > In Nov 2009 Cindy responded to a thread concerning ZFS device > issues, cfgadm, and mpxio: > > http://mail.opensolaris.org/pipermail/zfs-discuss/2009-November/033496.html > > <snip> >-- Bryan Hodgson Lehigh University Systems Manager Computer Science & Engineering bryan.hodgson at lehigh.edu Packard Lab 019 room 115 610-758-5001 19 Memorial Drive West Bethlehem, PA 18015-3016
On Nov 5, 2010, at 8:16 AM, Bryan Hodgson wrote:> > Folks, > > I''m trying to figure out whether we should give ZFS / mpxio a shot > on one of our research servers, or simply skip it (as we have > previously). > > In Nov 2009 Cindy responded to a thread concerning ZFS device > issues, cfgadm, and mpxio: > > http://mail.opensolaris.org/pipermail/zfs-discuss/2009-November/033496.html > > I''ve got an x2270 with the Sun EZ-SAS HBA and external SATA JBODs > (not J4xxx). The external disks simply provide bulk storage; lousy > performance is not a concern, reliability is. For obscure reasons, > we''re going to destroy / re-create those pools.There is an easy answer here -- SATA disks only use one path, so you don''t have to worry about mpxio at all. SAS disks should pick up mpxio by default. -- richard ZFS Tutorial at USENIX LISA''10 Conference next Monday www.RichardElling.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20101105/be08a112/attachment.html>