Hannes, I am working the firmware and management software folks to find out how to mine for this information. In your patch, the controller serial number may be helpful, but not necessarily compliant? Besides persistent device id, what else is gained? The controller ensures persistent device id for the arrays through the meta-data, only migrating if it happens to be a foreign (from another controller) array that collides with a native array at the same ID. Plug the constituent drives into totally different IDs in the SAS infrastructure, the ID remains the same as presented by the controller. Plug those drives into another controller, and if not taken by an existing array, the ID will again remain the same. If this is all of your concerns, adding the baggage to the driver will be redundant. Sincerely -- Mark Salyzyn > Hannes Reinecke wrote: > > Hi Mark, > > > > I found to my surprise that the aacraid driver does not support VPD > > pages at all. I'm somewhat used to modern SCSI HBAs export SCSI-2 disks, > > but not supporting VPD pages at all is really a bit .. hmm .. SCSI-1-ish. > > And it makes it really impossible to assign a persistent device ID to > > those drives. > > > [ .. ] > > > > Anyway, I don't think that it should be too hard to add proper VPD page > > support (ie page 0x83), but for that one would have some documentation > > how to ask the controller for it. I'll leave that to you :-) > > You can use the page 0x80 support as a template. > > And here is even the patch, based on scsi-misc. > Might help on reviewing. > > Cheers, > > Hannes > -- > Dr. Hannes Reinecke hare@xxxxxxx > SuSE Linux Products GmbH S390 & zSeries > Maxfeldstraße 5 +49 911 74053 688 > 90409 Nürnberg http://www.suse.de - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
