This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] vscsi and /dev/tape/by-path

To: "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
Subject: RE: [Xen-devel] vscsi and /dev/tape/by-path
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Wed, 12 Jan 2011 09:27:24 +1100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 11 Jan 2011 14:28:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110111220057.GA11945@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D01BB8F16@trantor> <20110111173724.GC14017@xxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01BB8F39@trantor> <20110111220057.GA11945@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acux21AaTgxBxfoASUaUgfB7ft5WDgAA0RYQ
Thread-topic: [Xen-devel] vscsi and /dev/tape/by-path
> > For disk, /dev/disk/by-uuid might be a better option, although it
> > depends on your requirements. For tape, my system /dev/tape/by-path
> > the only available option on my system, although I could probably
> > a /dev/tape/by-id path easily enough using the serial number or
> > something. by-id would allow the device to be moved across different
> > busses and still remain the same, but obviously breaks when a tape
> > fails and has to be replaced, which happens fairly regularly.
> So could the fix you are thinking of, check both of those places?
> What would the syntax end up for the vSCSI? I presume not SCSI ID
> but now just the UUID (or perhaps the SCSI inq S/N? ?)

Well all of those entries are just symlinks back to the /dev/stX or
/dev/sdX etc device, do I don't think we need to do anything else other
than follow the symlinks. I used os.realpath() (I think that was it) and
it works fine. I was just wondering if that was the right solution.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>