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

Re: [Xen-users] Problem iscsi on domU


  • To: "Lino Moragon" <lino.moragon@xxxxxxxxxxxx>
  • From: "Todd Deshane" <deshantm@xxxxxxxxx>
  • Date: Wed, 2 Jul 2008 15:40:58 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 02 Jul 2008 12:41:39 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:references; b=vGP/LFUUrnPhTWtzNcoiMJH9xI73Osl0S0Y+CN1jU1eWQUehyM2AX0ApPEK4wR+RHV fE0qbdEREzFHBbF5+ZK4Mqsn2Bt7T6iDm7VAAGQA6BJPsU8K7mETZoLY5H/1+oEYRdnS 12Hwht3me8H6aNa4r48WeHhiwmEerUz1Uz4m8=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>



On Wed, Jul 2, 2008 at 3:59 AM, Lino Moragon <lino.moragon@xxxxxxxxxxxx> wrote:
Todd Deshane wrote:



On Tue, Jul 1, 2008 at 2:36 AM, Lino Moragon <lino.moragon@xxxxxxxxxxxx <mailto:lino.moragon@xxxxxxxxxxxx>> wrote:

   Todd Deshane wrote:



       On Mon, Jun 30, 2008 at 5:46 AM, Lino Moragon
       <lino.moragon@xxxxxxxxxxxx <mailto:lino.moragon@xxxxxxxxxxxx>
       <mailto:lino.moragon@xxxxxxxxxxxx
       <mailto:lino.moragon@xxxxxxxxxxxx>>> wrote:

          Hi list,

          I'm having troubles to get an iscsi initiator working on a
       domU.
          As dom0 and domU I use a Centos 5 with the 2.6.18-53.1.14.el5
          xen-kernel.
          As iscsi initiator i use the iscsi-initiator-utils of the
       Centos5
          repo.
          The problem is, that when I log in to my iscsi target on
       the domU
          it is recognized as /dev/sda1.
          Now sda1 is also my root partition on the domU. And when I
       mount
          it I've mounted the root partition and not the iscsi device.

          Has anyone had this problem yet? Is there a solution to make it
          recognized as e.g. /dev/sdb ?

          Any help and tips would be appreciated.


       You should be able to setup a udev rule that will recognize
       the drives and correctly set them up.

       take a look here:
       http://www.performancemagic.com/iscsi-xen-howto/iSCSI.html

   Hi,

   Thanks for your response. I just tried it that way.
   Only problem is, that it creates a link that links to the same
   /dev/sda1.
   So if I mount the new /dev/iscsi_11 device it will mount again the
   root filesystem.
   Are there other possible options? Or isn't it at all possible?


Take a look at:
/dev/disk/by-uuid/
If I look at by-uuid i only get my "real" scsi device:
lrwxrwxrwx 1 root root 10 Jul  2 08:49 efd01d87-9b04-4d65-976c-cea045f51137 -> ../../sda1

Also for the by-id:
lrwxrwxrwx 1 root root 10 Jul  2 08:49 efd01d87-9b04-4d65-976c-cea045f51137 -> ../../sda1

And for the path there is my iscsi entry:
lrwxrwxrwx 1 root root 10 Jul  2 08:50 ip-172.16.10.70:3260-iscsi-iqn.1994-05.com.redhat:storage.mysql-part1 -> ../../sda1

But it is also linked to sda1 ... Problem is that udev doesn't seem to create a "new" block device like sdb...

Any ideas?


Just to be clear, this is on the domU right?

The iSCSI device *should* show up as a new scsi device like you want (i.e sdb etc.).

If it is not that seems like a bug in the domU kernel. Try exporting the iSCSI device to another computer or guest with a different kernel.

This kind of thing should work, I haven't used it regularly for a couple years, but it worked pretty well then, so it should work even better now.

Cheers,

Todd Deshane
http://todddeshane.net
check out our book: runningxen.com
_______________________________________________
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®.