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


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

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] vscsi and /dev/tape/by-path
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Tue, 11 Jan 2011 13:41:29 +1100
Delivery-date: Mon, 10 Jan 2011 18:42:17 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcuxOQzmYBqDHtHwTV6Lt9Sp1R3UnA==
Thread-topic: vscsi and /dev/tape/by-path
I use vscsi fairly extensively (under Windows mainly for testing
baremetal restores from tape), and have a problem that's been bugging me
for ages. If I use "/dev/st4" it works fine, but obviously that's
hopeless unreliable as it relies on device enumeration order at boot. I
want to use something like "
/dev/tape/by-path/pci-0000:01:08.0-scsi-0:0:3:0-st" so that I am
guaranteed of getting the right drive, but vscsi doesn't appear to
support it.

Digging into it, I see function vscsi_get_hctl_and_devname_by that
attempts to figure out the sg device that corresponds to whatever I
specified in the config file. If I could modify that function to simply
follow the symlinks until I get to a real device that would probably be
sufficient, but is that the right way to do it?



Xen-devel mailing list

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