On Thu, 02 Jul 2009 18:30:42 -0700 Marion Hakanson <[email protected]> wrote:
> [email protected] said: > > The first bug you mentioned 6851364 mpt driver is not configuring > > multipathing against SATA drives loaded on a (J4400). > > > > was closed for exactly the reason above - the disks were producing ASCII > > guids, not binary - and mpt doesn't allow such devices to be enumerated > > under > > scsi_vhci / MPxIO. > > > > From your initial post, it seems that you've got those same drives. > > True, we do have those drives, yet those exact drives are listed as > supported for multipathing, in the J4200/J4400 release notes dated > June-2009, that I quoted in an earlier note. Someone really should > fix the documentation, if the firmware really is faulty. I think you should mention to your support engineer that there is a very clear doc bug which needs immediate attention. > Since the drive firmware upgrade from 3AZQ to 3AZY evidently didn't help, > maybe we'll get them to send us 24 different drives that _do_ work. That's > a lot of "zpool replace" exercise, think I'd prefer new firmware.... Changing the firmware to deliver binary GUIDs rather than ascii would result in the devids changing, which would require the same zpool replace thumb-twiddling. > Hmm, if mpt-compatible firmware ever becomes available, and it _is_ going to > change the GUID/devid, would it be sufficient to "zpool export" everything > before applying such a drive firmware upgrade? Um, not sure, sorry. James -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog Kernel Conference Australia - http://au.sun.com/sunnews/events/2009/kernel _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
