On May 30, 10:29 am, Konrad Rzeszutek <[EMAIL PROTECTED]> wrote:
 > If you run iSCSI on each guests you end up with overhead.

I decided the same. So I'm running iscsi on the host, and via 
/dev/disk/by-path/whatever provide the guests with SAN storage.

Bad thing there, for each virtual disk of the san, I get two /dev 
entries, so I'm wondering how to setup the multipath over those two 
/dev/disk/by-path entries (one over each controller).

I also noticed the IPv^ thing, so I ended up specifying the IP by hand, 
and using to iscsiadm commands for each discovery / session initiation. 
Also, as you said, link aggregation makes no sense over crossover and 
two different interfaces.

What I'm NOT doing, is LVM. I wanted to go one layer at a time, and 
adding LVM was too much for my limited time in here.

So, currently, I have two remaining issues:

1) setup multipath
2) **URGENT**: I've added a second virtual disk and mapped it to my host 
(SAN is an MD3000i, host is ubuntu server with 2.6.24-17, i'm waiting 
for 2.6.25 which fixes the skb broadcast bug it seems).
If I use hwinfo, I can see the virtual disk (over /dev/sdc and the 2nd 
entry, /dev/sdf). Over fdisk, I get NOTHING.

Here's the dmesg output, hwinfo output, and fdisk output:

HWINFO
======
40: SCSI 300.1: 10600 Disk
  [Created at block.222]
  Unique ID: uBVf.EABbh0DH0_1
  SysFS ID: /block/sdc
  SysFS BusID: 3:0:0:1
  SysFS Device Link: /devices/platform/host3/session1/target3:0:0/3:0:0:1
  Hardware Class: disk
  Model: "DELL MD3000i"
  Vendor: "DELL"
  Device: "MD3000i"
  Revision: "0670"
  Serial ID: "84L000I"
  Driver: "sd"
  Device File: /dev/sdc (/dev/sg4)
  Device Files: /dev/sdc, 
/dev/disk/by-id/scsi-36001e4f00043a3da000004dc4843982f, 
/dev/disk/by-path/ip-192.168.131.101:3260-iscsi-iqn.1984-05.com.dell:powervault.6001e4f0004326c100000000482127e3-lun-1
  Device Number: block 8:32-8:47 (char 21:4)
  Geometry (Logical): CHS 102400/64/32
  Size: 209715200 sectors a 512 bytes
  Drive status: no medium
  Config Status: cfg=new, avail=yes, need=no, active=unknown

That "drive status: no medium" drives me crazy. For comparison, this is 
the output for the first virtual disk I created, the one I can access:

41: SCSI 300.0: 10600 Disk
  [Created at block.222]
  Unique ID: R0Fb.EABbh0DH0_1
  SysFS ID: /block/sdb
  SysFS BusID: 3:0:0:0
  SysFS Device Link: /devices/platform/host3/session1/target3:0:0/3:0:0:0
  Hardware Class: disk
  Model: "DELL MD3000i"
  Vendor: "DELL"
  Device: "MD3000i"
  Revision: "0670"
  Serial ID: "84L000I"
  Driver: "sd"
  Device File: /dev/sdb (/dev/sg3)
  Device Files: /dev/sdb, 
/dev/disk/by-id/scsi-36001e4f0004326c1000005b3483e9c7a, 
/dev/disk/by-path/ip-192.168.131.101:3260-iscsi-iqn.1984-05.com.dell:powervault.6001e4f0004326c100000000482127e3-lun-0
  Device Number: block 8:16-8:31 (char 21:3)
  Geometry (Logical): CHS 261/255/63
  Size: 4194304 sectors a 512 bytes
  Config Status: cfg=new, avail=yes, need=no, active=unknown

DMESG
=====

end_request: I/O error, dev sdc, sector 209715192
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 209715192
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 209715192
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 209715192
Buffer I/O error on device sdc, logical block 26214399
end_request: I/O error, dev sdc, sector 209715192
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 209715192
end_request: I/O error, dev sdc, sector 0

The attach-time messages got lost, but I remember this line:
Dev sdc: unable to read RDB block 0

FDISK
=====
[EMAIL PROTECTED]:~# fdisk -l /dev/sdc
[EMAIL PROTECTED]:~# fdisk /dev/sdc

Unable to read /dev/sdc

Might the disk still be initializing? The Dell client says it's finished...

Thanks!!


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to