-
Block Size
Hello,
i have been testing Red Hat Enterprise Virtualization 3 beta with Open-E VSS 6 as a iscsi Storage.
The problem is now, that Red Hat Enterprise Virtualization 3 beta can't attach a Open-E VSS 6 iscsi lun, because there block size is bigger than 512bytes (Red Hat Enterprise Virtualization 3 beta supports only 512bytes LUN's).
My Question is now, how i can create a iscsi 512bytes block size LUN in Open-E VSS 6?
thanks.
-
Hi. I'm almost 100% that the blocksize is 512. The only location where block size can be changed is for FC targets.
Are you sure that is your issue? Can you provide a dmesg output after you've connected to the iSCSI target?
-
Thanks for answer.
The problem is that i can't attach the LUN, because there is not a 512bytes block size.
Here is a picture of the failure:
http://imageshack.us/photo/my-images/716/rh3testa.jpg
:-(
-
i hava a update.
I have not issue when i use the "iet" target or "scst vpd 1.0".
Only i have with "scst vpd 2.0" this block size error.
Why?
-
I think i have found the bug...
SCST VPD 1.0:
I have attach this to Red Hat Enterprise Linux 6.2:
Platte /dev/sdb: 34.3 GByte, 34292629504 Byte
64 Köpfe, 32 Sektoren/Spur, 32704 Zylinder
Einheiten = Zylinder von 2048 × 512 = 1048576 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Jan 16 16:00:04 localhost kernel: connection10:0: detected conn error (1020)
Jan 16 16:00:04 localhost kernel: scsi13 : iSCSI Initiator over TCP/IP
Jan 16 16:00:04 localhost iscsid: Connection10:0 to [target: iqn.2012-01:dsstest.target6, portal: 10.21.32.200,3260] through [iface: default] is shutdown.
Jan 16 16:00:04 localhost kernel: scsi 13:0:0:0: Direct-Access SCST_BIO CVTjrfRmPxVzoKGe 101 PQ: 0 ANSI: 4
Jan 16 16:00:04 localhost kernel: sd 13:0:0:0: Attached scsi generic sg2 type 0
Jan 16 16:00:04 localhost kernel: sd 13:0:0:0: [sdb] 66977792 512-byte logical blocks: (34.2 GB/31.9 GiB)
Jan 16 16:00:04 localhost kernel: sd 13:0:0:0: [sdb] Write Protect is off
Jan 16 16:00:04 localhost kernel: sd 13:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jan 16 16:00:04 localhost kernel: sdb: unknown partition table
Jan 16 16:00:04 localhost kernel: sd 13:0:0:0: [sdb] Attached SCSI disk
Jan 16 16:00:05 localhost iscsid: Connection11:0 to [target: iqn.2012-01:dsstest.target6, portal: 10.21.32.200,3260] through [iface: default] is operational now
SCST VPD 2.0:
I have attach this to Red Hat Enterprise Linux 6.2:
Platte /dev/sdb: 30.8 GByte, 30836523008 Byte
64 Köpfe, 32 Sektoren/Spur, 29408 Zylinder
Einheiten = Zylinder von 2048 × 512 = 1048576 Bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes
Disk identifier: 0x00000000
Jan 16 16:14:46 localhost kernel: connection14:0: detected conn error (1020)
Jan 16 16:14:46 localhost kernel: scsi17 : iSCSI Initiator over TCP/IP
Jan 16 16:14:47 localhost iscsid: Connection14:0 to [target: iqn.2012-01:dsstest.target3, portal: 10.21.32.200,3260] through [iface: default] is shutdown.
Jan 16 16:14:47 localhost kernel: scsi 17:0:0:0: Direct-Access SCST_BIO 6Wf6W6WPjOV2J27z 200 PQ: 0 ANSI: 5
Jan 16 16:14:47 localhost kernel: sd 17:0:0:0: Attached scsi generic sg2 type 0
Jan 16 16:14:47 localhost kernel: sd 17:0:0:0: [sdb] 60227584 512-byte logical blocks: (30.8 GB/28.7 GiB)
Jan 16 16:14:47 localhost kernel: sd 17:0:0:0: [sdb] 4096-byte physical blocks
Jan 16 16:14:47 localhost kernel: sd 17:0:0:0: [sdb] Write Protect is off
Jan 16 16:14:47 localhost kernel: sd 17:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jan 16 16:14:47 localhost kernel: sdb: unknown partition table
Jan 16 16:14:47 localhost kernel: sd 17:0:0:0: [sdb] Attached SCSI disk
Jan 16 16:14:48 localhost iscsid: Connection15:0 to [target: iqn.2012-01:dsstest.target3, portal: 10.21.32.200,3260] through [iface: default] is operational now
This is a interesting Line:
by SCST VPD 1.0:
Sector size (logical/physical): 512 bytes / 512 bytes
by SCST VPD 2.0:
Sector size (logical/physical): 512 bytes / 4096 bytes
I think that the physical sector size of 4096 bytes is the problem, but how i can fix this?
-
Ahh yes. Go ahead and set it to VPD to 1. You won't loose any functionality or performance.
-
But what is the difference of SCST VPD 1.0 and SCST VPD 2.0?
When both the same, why SCST VPD 2.0?
-
the VPD value sets the way the device is identified. VPD=2 is the new way in SCST, VPD=1 is the old way and compatible to IET identities.