WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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 08:00:47 +1100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 11 Jan 2011 13:04:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110111173724.GC14017@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acuxtk1PY70+Fdu1Rg2/cCStEqEBTAAG9alw
Thread-topic: [Xen-devel] vscsi and /dev/tape/by-path
> 
> On Tue, Jan 11, 2011 at 01:41:29PM +1100, James Harper wrote:
> > 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?
> 
> Yup. Thought I would think that using the /dev/by-uuid/ would be a
better
> way of doing it in case you want to passthrough a SCSI disk for
example?
> 

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 is
the only available option on my system, although I could probably create
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 drive
fails and has to be replaced, which happens fairly regularly.

This is the advantage of having so many choices :)

> Thought what if you want to pass in a SCSI scanner? Would that work?

Do they still exist? :)

James


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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