This post is more than 5 years old
3 Posts
0
2820
blkScsi_Inquiry_CK: Unsupported Inquiry page-code 0x84
ScaleIO 2.0.1.3
CentOS 6.8
Kernel: 2.6.32-642.el6.x86_64
Structure: 2-layer with standalone SDC nodes
While testing ScaleIO with Oracle running on its volume, we see a lot of following errors in /var/log/messages of SDC nodes:
Cmd ffff880aeabb6781: Unsupported Inquiry page-code 0x84
Jan 26 16:03:00 b201i23rs01 kernel: ScaleIO R2_0 blkScsi_Inquiry_CK:405 :Error: Cmd ffff880aeabb60a1: Unsupported Inquiry page-code 0x84
Jan 26 16:03:00 b201i23rs01 kernel: ScaleIO R2_0 blkScsi_Inquiry_CK:405 :Error: Cmd ffff880e198a7741: Unsupported Inquiry page-code 0x84
Jan 26 16:03:00 b201i23rs01 kernel: ScaleIO R2_0 blkScsi_Inquiry_CK:405 :Error: Cmd ffff880e198a7741: Unsupported Inquiry page-code 0x84
Jan 26 16:03:00 b201i23rs01 kernel: ScaleIO R2_0 blkScsi_Inquiry_CK:405 :Error: Cmd ffff880e198a7741: Unsupported Inquiry page-code 0x84
Jan 26 16:03:00 b201i23rs01 kernel: ScaleIO R2_0 blkScsi_Inquiry_CK:405 :Error: Cmd ffff880e198a7741: Unsupported Inquiry page-code 0x84
It seems that ScaleIO does not recognize some SCSI commands.
Is there any SCSI operations that ScaleIO does not support?
Thanks
Message was edited by: vespasianvs
pawelw1
306 Posts
0
February 6th, 2018 02:00
Hi,
Yes, we don't support this particular INQ page code. And yes, there are many SCSI commands ScaleIO doesn't support - just like every other array ;-) It is impossible to support all of them, many are deprecated, many are vendor/product specific etc.
I might talk to Development if we can supress these messages in one of the newer versions, but for the time being they can be simply ignored.
Hope it helps.
Cheers,
Pawel
Vespasianvs
3 Posts
0
February 6th, 2018 07:00
I did a test by using sg_vpd to query page 0x84 from a scaleio volume, and saw the exact same error messages in /var/log/messages.
[root@alex-sio1 ~]# sg_vpd -l --page 0x83 /dev/scinia
Device Identification VPD page:
[PQual=0 Peripheral device type: disk]
Addressed logical unit:
designator type: EUI-64 based, code set: Binary
EUI-64 based 16 byte identifier
Identifier extension: 0x6a49f84d2398d4b5
IEEE Company_id: 0xee3bd1
Vendor Specific Extension Identifier: 0x6a00000000
[root@alex-sio1 ~]# sg_vpd -l --page 0x84 /dev/scinia ; date
Software interface identification VPD page:
sense buffer empty
fetching VPD page failed
Tue Feb 6 23:10:23 CST 2018
[root@alex-sio1 ~]# tail /var/log/messages | grep 23:10:23
Feb 6 23:10:23 alex-sio1 kernel: ScaleIO R2_0 blkScsi_Inquiry_CK:405 :Error: Cmd ffff8803c47ae601: Unsupported Inquiry page-code 0x84
Vespasianvs
3 Posts
0
February 6th, 2018 07:00
Pawel, thanks for the answer. I also did some research and found out more details about "page-code x84".
Per http://sg.danny.cz/sg/sdparm.html, manual of sdparm and sg_vpd (part of sg3_utils package).
Vital Product Data (VPD) pages are fetched with the SCSI INQUIRY command. While support for a "standard" INQUIRY response is mandatory, support for VPD page has been optional in the past. SPC-2 (which became a standard in 2001) and SPC-3 (ANSI INCITS 408-2005) made support for the "Device Identification" and the "Supported VPD pages" VPD pages mandatory. A utility like sdparm should be able to send an INQUIRY command and get a valid response when the target device or logical unit is in almost any state. SCSI devices are not required to respond to mode pages accesses when the device is in any state For example, often disk drives will not allow mode pages to be accessed or changed when the disk is spun down.
VPD pages are read only and in some situations may not be available (e.g. if the media is spun down or not present). Even in such cases the INQUIRY command should still respond with perhaps zero in the affected fields. VPD pages tend to have a variable number of descriptors rather than a predictable size with parameters in known positions such as most mode pages.
Here are some of the VPD pages that are currently decoded (listed in page number order):
[page 0x83] Device identification default; Contains designators for the addressed logical unit, target device and target port.
[page 0x84] Software Interface Identification; one or more EUI-48 identifiers that can be used to define more precisely the peripheral device type.
pawelw1
306 Posts
0
February 7th, 2018 04:00
Nice test, thank you for sharing!
Pawel