Hi Nicholas,
The kernel on the target server is 3.6.3-1.fc17.x86_64
I have been playing with it trying to figure it out over the last day,
including removing the target and trying to recreate it, which all
ended in the same result. Here is the error message and 'sg_inq -i
/dev/sdX' output for that new target.
Oct 30 21:35:06 hydra-2-ss-storage-appliance-1 udevd-work[21950]:
symlink(../../sda,
/dev/disk/by-id/scsi-30103ff1060014053a4c9495036c94f81ffffffff020100184c494f2d4f52470049424c4f434b3a3361346339343935005194ff04000000025195000408ab0000018eff04000000005398005069716e2e323030332d30312e6f72672e6c696e75782d69736373692e68796472612d322d646576696365732d686f73742e78.udev-tmp)
failed: File name too long
[root@hydra-2-ss-storage-appliance-1 ~]# sg_inq -i /dev/sda
VPD INQUIRY: Device Identification page
Designation descriptor number 1, descriptor length: 20
designator_type: NAA, code_set: Binary
associated with the addressed logical unit
NAA 6, IEEE Company_id: 0x1405
Vendor Specific Identifier: 0x3a4c94950
Vendor Specific Identifier Extension: 0x36c94f81ffffffff
[0x60014053a4c9495036c94f81ffffffff]
Designation descriptor number 2, descriptor length: 28
designator_type: T10 vendor identification, code_set: ASCII
associated with the addressed logical unit
vendor id: LIO-ORG
vendor specific: IBLOCK:3a4c9495
Designation descriptor number 3, descriptor length: 8
transport: Internet SCSI (iSCSI)
designator_type: Relative target port, code_set: Binary
associated with the target port
Relative target port: 0x2
Designation descriptor number 4, descriptor length: 8
transport: Internet SCSI (iSCSI)
designator_type: Target port group, code_set: Binary
associated with the target port
Target port group: 0x0
Designation descriptor number 5, descriptor length: 8
designator_type: Reserved [0xe], code_set: Binary
associated with the addressed logical unit
00 30 00 00 00 0...
Designation descriptor number 6, descriptor length: 84
transport: Internet SCSI (iSCSI)
designator_type: SCSI name string, code_set: UTF-8
associated with the target port
SCSI name string:
iqn.2003-01.org.linux-iscsi.hydra-2-devices-host.x8664:sn.5c839069c550,t,0x0001
Hope that helps,
Kelsey
On Wed, Oct 31, 2012 at 12:00 PM, Nicholas A. Bellinger
<nab@xxxxxxxxxxxxxxx> wrote:
> On Tue, 2012-10-30 at 15:48 +0000, Prantis, Kelsey wrote:
>> Hello,
>>
>
> Hi Kelsey,
>
>> This is my first time using targetcli. In my setup I have several
>> Centos VMs as iscsi initiators, and a single Fedora VM I am using for
>> the portal. When I attempt discovery on the initiators, I am getting
>> messages in /var/log/messages like the following for all of my
>> targets:
>>
>> Oct 30 05:22:31 hydra-2-ss-storage-appliance-1 udevd-work[2979]:
>> symlink(../../sdb, /dev/disk/by-id/scsi-30103ff106001405927a2fe3c7b644d59135dfc1d020100344c494f2d4f52470049424c4f434b3a39323761326665332d633762362d343464352d393133352d6466633164343766633534370051940004000000015195fe040088000001060004000000005398005069716e2e323030332d30312e6f72672e6c696e75782d.udev-tmp) failed: File name too long
>>
>> Is there a way I can set this id to guarantee it is not too long? Or
>> is this indicative of some deeper issue I need to fix?
>>
>
> Hmmmm. Could you verify which Fedora kernel is in use on the target VM
> in question..?
>
> Also, what does the 'sg_inq -i /dev/sdX' output look like from the
> CentOS open-iscsi initiator VMs side..?
>
> Thanks for reporting!
>
> --nab
>
> --
> 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
--
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
