piyush agrawal wrote: > Hi all, > > I have created FCoE initiator and target setup on 2 separate machines(not > VMs).I have exported 2 luns from target.Following is the part of dmesg dump > at initiator side. from that > i can say that initiator has discovered luns. but i cant see any lun after > fdisk -l at initiator side itself. > > > [ 447.688858] sd 4:0:0:0: [sdb] 4096 512-byte hardware sectors (2 MB) > [ 447.689220] sd 4:0:0:0: [sdb] Write Protect is off > [ 447.689306] sd 4:0:0:0: [sdb] Mode Sense: 83 00 10 08 > [ 447.689845] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, > supports DPO and FUA > [ 447.691408] sd 4:0:0:0: [sdb] 4096 512-byte hardware sectors (2 MB) > [ 447.691800] sd 4:0:0:0: [sdb] Write Protect is off > [ 447.691873] sd 4:0:0:0: [sdb] Mode Sense: 83 00 10 08 > [ 447.693392] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, > supports DPO and FUA > [ 447.693526] sdb: unknown partition table > [ 447.697173] sd 4:0:0:0: [sdb] Attached SCSI disk > [ 447.701062] fc_fcp_resp short FCP response. flags 0x8 len 36 respl 0 snsl > 0
This message indicates a problem. The flag in the response from the target indicates there was an underrun, but the response isn't long enough to hold a residual count. This seems like an SCST bug. I'm guessing this is because space wasn't pre-allocated for the vdisks. If I recall, you need to dd to the backing file to the vdisk to get the space pre-alloaced. I haven't rechecked this, but that's where I'd look. > [ 447.701425] scsi 4:0:0:1: Direct-Access SCST_FIO vdisk2 > 101 PQ: 0 ANSI: 4 > [ 447.707399] sd 4:0:0:1: [sdc] 2048 512-byte hardware sectors (1 MB) > [ 447.709068] sd 4:0:0:1: [sdc] Write Protect is off > [ 447.709155] sd 4:0:0:1: [sdc] Mode Sense: 83 00 10 08 > [ 447.713068] sd 4:0:0:1: [sdc] Write cache: enabled, read cache: enabled, > supports DPO and FUA > [ 447.715410] sd 4:0:0:1: [sdc] 2048 512-byte hardware sectors (1 MB) > [ 447.717068] sd 4:0:0:1: [sdc] Write Protect is off > [ 447.717155] sd 4:0:0:1: [sdc] Mode Sense: 83 00 10 08 > [ 447.725408] sd 4:0:0:1: [sdc] Write cache: enabled, read cache: enabled, > supports DPO and FUA > [ 447.725544] sdc: unknown partition table > [ 447.733935] sd 4:0:0:1: [sdc] Attached SCSI disk > [ 4821.163181] sd 4:0:0:0: [sdb] Synchronizing SCSI cache > [ 4821.163285] sd 4:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT > driverbyte=DRIVER_OK,SUGGEST_OK > [ 4821.163420] sd 4:0:0:1: [sdc] Synchronizing SCSI cache > [ 4821.163502] sd 4:0:0:1: [sdc] Result: hostbyte=DID_NO_CONNECT > driverbyte=DRIVER_OK,SUGGEST_OK > > > Does this interpret anything that where i am getting wrong? I am creating > virtual disks (vdisk). Should i do anything extra to see that luns after > fdisk -l. Or is there any other way to perform actions on those luns? > I am using kernel 2.6.23 at target side and 2.6.27 at initiator side. > Thanking in advance.. > _______________________________________________ > devel mailing list > [email protected] > http://www.open-fcoe.org/mailman/listinfo/devel _______________________________________________ devel mailing list [email protected] http://www.open-fcoe.org/mailman/listinfo/devel
