On 02.05.2017 12:34, Stefan Haberland wrote:
Hi Marcy,
May 01 18:12:35 cdzea02a9919 kernel: dasd-eckd.b3193d: 0.0.8006: An
error occurred in the DASD device driver, reason=09
May 01 18:12:35 cdzea02a9919 kernel: dasd(eckd): I/O status report
for device 0.0.8006:
                                      dasd(eckd): in req:
000000007d437ed8 CC:00 FC:04 AC:00 SC:17 DS:0E CS:00 RC:0
                                      dasd(eckd): device 0.0.8006:
Failing CCW: 000000007d437fe8
                                      dasd(eckd): Sense(hex)  0- 7:
80 00 00 00 00 00 00 0f
                                      dasd(eckd): Sense(hex) 8-15: ef
05 00 00 00 00 00 00
                                      dasd(eckd): Sense(hex) 16-23:
00 00 00 00 3a 00 0f 00
                                      dasd(eckd): Sense(hex) 24-31:
00 00 60 e0 00 00 00 00
                                      dasd(eckd): 24 Byte: 0 MSG f,
no MSGb to SYSOP
May 01 18:12:35 cdzea02a9919 kernel: dasd(eckd): Related CP in req:
000000007d437ed8
                                      dasd(eckd): CCW
000000007d437fe0: 2760000C 7D437FF0 DAT:  18000000 46171c00 00000000
                                      dasd(eckd): CCW
000000007d437fe8: 3E20401A 513C0000 DAT:  00000000 00000000 00000000
0000000


The error code is generated by z/VM because it does not support a
command we newly use while formatting/partitioning a device.
You will also get it if you read the
/sys/bus/ccw/devices/0.0.XXXX/host_access_count sysfs attribute.
With this error message there is no other bad implication beside the
fact that the command we used was not working but that is OK.

You can ignore the message for now. It will be omitted (if possible)
or suppressed with an upcoming update.
The patch is already scheduled for upstream integration and should
also be included in SLES12 in a future update.

Kind regards,
Stefan

Hi,

its me again, sry I did not want to confuse you. I mixed something up.

It is still valid that the error message is caused by z/VM and they did
not like a command we used for some reason but the rest of the quick
analysis was not right.
The specific command I was thinking about is not there in SLES12SP2 it
is only upstream as of today. So please ignore the rest.

If you already opened a support ticket we have to take a closer look at
the error. Most likely someone from z/VM has to look at this.

Regards,
Stefan

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to