Hello,
Patch e270af8b3c3d6ff3dddc29667df69b691cc517c0
("target: remove custom hex2bin() implementation") causes that for the
same serial number, NAA reported in VPD 0x83 is different than NAA
before this patch. Which in turn confuses iSCSI storage clients like
VMware ESXi etc. after upgrade to the lastest LIO target code.
Before patch:
Device Identification VPD page:
Addressed logical unit:
designator type: NAA, code set: Binary
0x600140535a4c2c4daa90dd591dc453dd
designator type: T10 vendor identification, code set: ASCII
vendor id: LIO-ORG
vendor specific: IBLOCK:35a4c2c4-aa90-d591-c453-d8a60ff00000
After patch:
Device Identification VPD page:
Addressed logical unit:
designator type: NAA, code set: Binary
0x600140535a4c2c3faa90fd590fc453fd
designator type: T10 vendor identification, code set: ASCII
vendor id: LIO-ORG
vendor specific: IBLOCK:35a4c2c4-aa90-d591-c453-d8a60ff00000
I'm not sure which NAA should be the "right" one but the patch
definitely breaks NAA compatibility with previous LIO 4.1 code.
Reverting the patch fixes the problem for me.
Affected kernels: mainline 3.1-rc1, lio-core-2.6 master branch,
lio-4.1-3.0 branch.
Unaffected kernels: lio-4.1-2.6.39 branch and olders
Regards
Martin
--
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
