[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Re: Xen, LV, ISCSI and Persistent Target



Hello,

Another mean is to use the /dev/disk/by-path, the iscsi devices (XEN 3.1
on SLES 10 SP1). The "PATH" is made with IP,InitiatorName and name of
the LUN.
If no elements are changed the "PATH" stay the same.

Regards

JP Pozzi

> Message: 2
> Date: Mon, 17 Nov 2008 17:50:26 -0700
> From: Mike Lovell <mike@xxxxxxxxxxxx>
> Subject: Re: [Xen-users] Xen, LV, ISCSI and Persistent Target
> To: Chris Edwards <cedwards@xxxxxxxxxxxxxxxx>
> Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
> Message-ID: <49221152.3080506@xxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Chris Edwards wrote:
> > When setting up Xen to use a iSCSI target with raw logical volumes works 
> > great until I restart iSCSI and it changes the device name.   Can I use 
> > e2label to solve this problem or is there a way to set a persistent target?
> >
> > ---
> >
> > Chris Edwards
> >   
> e2label would probably be a sufficient way to doing that depending on 
> how your system does things with labels. Another option would be to use 
> udev to persist naming of the iscsi block devices. This is a link to a 
> tutorial I used about 2 years ago to do this.
> 
> http://www.performancemagic.com/iscsi-xen-howto/
> 
> The udev part of the iSCSI setup would probably be what would be 
> interesting for you. It worked for me. Probably could use a little bit 
> of updating as well but should give you an idea.
> 
> Mike
> 
> 
> 



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.