Rumor has it that on Thu, Jan 26, 2006 at 07:28:53PM +0100 Kurt Garloff said:
> Hi Philip,
> On Thu, Jan 26, 2006 at 09:20:40AM -0500, Philip R. Auld wrote:
> > Right, but this is just showing which UID it mapped to sda. My point
> > was you can configure it to give a specific name to a specific UID:
> > scsi-0ATA_ST3200826AS_Linux_ATA-SCSI_simulator -> ../../my_domU_diska
> > Then you use my_domU_disk in the xen domain configuration.
> > You can do this manually as well by looking up which sdX name the
> > deivce got and making a link it or device node with the same
> > major/minor. But I think udev can be configured to to it for you.
> > I don't know the details of how to make it do that, but that's part
> > of what it's for.
> disk = [ 'iscsi:scsi-0ATA_ST3200826AS_Linux_ATA-SCSI_simulator,hda,w' ]
> and drop a script into /etc/xen/scripts/block-iscsi
> that handles it. (I'm assuming now that scsi-0ATA_ST... is a unique
> identifier here; otherwise chose a different property of your iSCSI
> Unless I misunderstood something, that suggestion of Mark really
> solves your problem.
Thanks. But I don't have a problem (at least not this anyway ;).
We're both talking about different ways to do the same thing.
My point again is that udev can handle the task of creating
well-known, consistent device names for uniquely identifiable
disks. And that it makes sense to me to just configure udev
properly and you do not need to do anything xen specific to
solve this problem. And it is not iSCSI specific either.
As I said, I don't know for sure how to make udev do
this for iSCSI. For FC you can use the scsi_id callout to
get the UID and then have a udev rule to use to generate a
device name. There may not exist an analog of scsi_id for
iSCSI. It's the same as what you are suggesting except it's
Linux-wide and not xen only :)
> Kurt Garloff, Head Architect, Director SUSE Labs (act.), Novell Inc.
Philip R. Auld, Ph.D. Egenera, Inc.
Software Architect 165 Forest St.
(508) 858-2628 Marlboro, MA 01752
Xen-devel mailing list