Sorry... an update... using kernel 3.6.11 this issue doesn't happens and the disk looks good. Thanks all and sorry for disturb. Alessandro On Tue, 2013-02-19 at 08:42 +0100, Alessandro Musso wrote: > Hi all > i configured a iscsi target using targetcli 2.0 rc1 on Alpine Linux > Kernel 3.6.6-grsec. > I have a SAS storage (4TB) that i want to use as Cluster Shared Volume > in a WIndows Failover Cluster and Hyper-V. > > So this is the targetcli configuration. No problem at all. > o- / ......................................................................................................................... > [...] > o- backstores > .............................................................................................................. > [...] > | o- block ................................................................................................... > [1 Storage Objects] > | | o- fsdr .................................................................... > [/dev/vg01/lv_fsdr (4.3TiB) write-back activated] > | o- fileio ................................................................................................... > [0 Storage Object] > | o- pscsi .................................................................................................... > [0 Storage Object] > | o- ramdisk .................................................................................................. > [0 Storage Object] > o- iscsi ............................................................................................................. > [1 Targets] > | o- iqn.2003-01.org.linux-iscsi.itbak01.i686:sn.2d61bb8e9423 > ............................................................ [1 TPG] > | o- tpg1 ............................................................................................................ > [enabled] > | o- acls > ........................................................................................................... > [1 ACLs] > | | o- iqn.1991-05.com.microsoft:itvs02.dom.net > ......................................................... [1 Mapped > LUN] > | | | o- mapped_lun0 > .................................................................................. > [lun0 block/fsdr (rw)] > | o- luns > ........................................................................................................... > [1 LUNs] > | | o- lun0 > ................................................................................. > [block/fsdr (/dev/vg01/lv_fsdr)] > | o- portals > ..................................................................................................... > [2 Portals] > | o- 10.44.4.71:3260 > .................................................................................................. > [OK] > | o- 10.44.4.7:3260 > ................................................................................................... > [OK] > o- loopback .......................................................................................................... > [0 Targets] > > I connect a Windows Server 2008 R2 Initiator to this target. > So the problem is that after the connection, automatically appear a > volume, and not only the disk. THe volume type is "Removable", so i > can't delete it neither shrink nor add it as cluster shared volume to > the failover cluster. > > On windows server: > DISKPART> list disk > > Disk ### Status Size Free Dyn Gpt > -------- ------------- ------- ------- --- --- > Disk 0 Online 67 GB 0 B > Disk 1 Online 4442 GB 0 B <---------- disk > appear, this good > > DISKPART> list vol > > Volume ### Ltr Label Fs Type Size Status Info > ---------- --- ----------- ----- ---------- ------- --------- -------- > Volume 0 E DVD-ROM 0 B No Media > Volume 1 System Rese NTFS Partition 100 MB Healthy System > Volume 2 C NTFS Partition 67 GB Healthy Boot > Volume 3 D FS-DR NTFS Removable 4442 GB Healthy > <----- a removable volume appear, this not good > > > I did test with several machine (Windows server 2008 R2 and also > Windows 7) and the result is the same. > > When the iscsi initiator connect to the target dmesg said: > [291842.158077] MODE SENSE: unimplemented page/subpage: 0x1c/0x00 > [291842.220979] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.224671] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.326963] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.331955] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.356467] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.362361] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.496751] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.502637] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.558154] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.566791] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.656099] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > [291842.660544] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x1e, > sending CHECK_CONDITION. > > > I searched in internet but i did'n find any reference to this issue. > > Anyone have idea of the cause? > Thanks all -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
