From: lingli tang <tanglingli001@gmail.com>
To: Or Gerlitz <ogerlitz@mellanox.com>
Cc: Apollon Oikonomopoulos <apoikos@debian.org>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
STGT-Devel <stgt@vger.kernel.org>,
"Cullison, Dennis" <Dennis.Cullison@teradata.com>
Subject: Re: scsi_id not valid in iscsi node
Date: Mon, 23 Jun 2014 11:09:14 +0800 [thread overview]
Message-ID: <CAN+bsqh4NdGCoOa=eYyGFe3qTVww1rLPV_7CuB0VMDRP9G-Puw@mail.gmail.com> (raw)
In-Reply-To: <539D3BD2.4070904@mellanox.com>
so after commit 8141d67b. the tgtd is not Backward compatible?
and we have to use tgtd before commit 8141d67b for compatible with
multipath/udev of rhel6.2
or rebuild a different multipath/udev in rhel6.2?
2014-06-15 14:23 GMT+08:00 Or Gerlitz <ogerlitz@mellanox.com>:
> On 03/06/2014 09:09, Apollon Oikonomopoulos wrote:
>>
>> On 14:43 Mon 02 Jun , Nicholas A. Bellinger wrote:
>>>
>>> Forwarding to the correct stgt-devel list..
>>>
>>> On Fri, 2014-05-30 at 17:38 +0800, lingli tang wrote:
>>>>
>>>> [...]
>>>> 1. [...] cpu（%user,%sys,%iowait,%idle）,memory(Total，used, free,
>>>>
>>>> buffer, cache), IOPS(read request, write request), Througthput(read
>>>> kb, write kb)，
>>>>
>>>> we use tgtd 1.0.47 to export a disk and use iscsiadm to load it.
>>>> but the ID_SERIAL of this disk is not the same with scsi_id of export
>>>> disk.
>>>> if we use tgtd 1.0.24 it is the same.
>>>> after iscsiadm log in, we check the ID_SERIAL of this disk using
>>>> “udevadm info --query=all --path=/block/sdb”：
>>>> E: ID_SERIAL_RAW=360000000000000000e001000c00000e0
>>>> E: ID_SERIAL=360000000000000000e001000c00000e0
>>>> E: ID_SERIAL_SHORT=60000000000000000e001000c00000e0
>>>>
>>>> but with tgtd 1.0.24, it is correct:
>>>> E: ID_SERIAL_RAW=1test1-iscsi-iser
>>>> E: ID_SERIAL=1test1-iscsi-iser
>>>> E: ID_SERIAL_SHORT=test1-iscsi-iser
>>>>
>>>> test environment rhel6.2
>>
>> We were debugging the exact same thing yesterday, after our persistent
>> links under /dev stopped working, so here's the short version of the
>> story:
>>
>> Commit 6402eb8 added an NAA local designator (WWN) field to tgt's 0x83
>> VPD (the Device Identification page), and commit 8141d67b further added
>> an extended WWN. All three identifiers are sent out in tgt's 0x83 VPD,
>> but udev's scsi_id helper always picks the binary WWN by preference and
>> uses it as ID_SERIAL, i.e. ignores the ASCII T10 (ID_SERIAL) identifier
>> present in the VPD. If you use sg_inq from the sg3-utils package you
>> will get both.
>>
>> I'm not sure tgt can do much more than make both NAA identifiers
>> optional, the issue seems to lie with udev at this point.
>>
>>
>
> I added Dennis who is the author of commit 8141d67b -- he made the following
> comment: "[...] This is most likely an issue with udev. Most of the udev
> tools look at Inquiry VPD 0x83 before looking at VPD 0x80. With the NAA
> pages now defined in VPD 0x83, the tools are using that information instead
> of VPD 0x80."
prev parent reply other threads:[~2014-06-23 3:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN+bsqg+rrCRHci=8K8_Az6EjONByTuadOGw-NfXdgjQSAvT_A@mail.gmail.com>
2014-06-02 21:43 ` scsi_id not valid in iscsi node Nicholas A. Bellinger
2014-06-03 6:09 ` Apollon Oikonomopoulos
2014-06-10 4:44 ` lingli tang
2014-06-15 6:23 ` Or Gerlitz
2014-06-23 3:09 ` lingli tang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN+bsqh4NdGCoOa=eYyGFe3qTVww1rLPV_7CuB0VMDRP9G-Puw@mail.gmail.com' \
--to=tanglingli001@gmail.com \
--cc=Dennis.Cullison@teradata.com \
--cc=apoikos@debian.org \
--cc=nab@linux-iscsi.org \
--cc=ogerlitz@mellanox.com \
--cc=stgt@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).