Re: Virtual device

2020-10-22 Thread Tully, Phil (CORP)
Sorry the log I was given was cut off "dasd-eckd.fe3f84: 0.0.0191: Not all channel paths lead to the same device, path 40 leads to device EMC.09000ATVHC.3000.0f.000101f4 instead of EMC.09000ATVHC.3000.0f" "dasd-eckd.fe3f84: 0.0.0191: Not all channel paths lead

Re: Virtual device

2020-10-22 Thread Stefan Haberland
Hi, yes, this is at least used to uniquely identify minidisk based DASD devices in Linux under z/VM. On LPAR you will not find this part. Am 22.10.20 um 16:09 schrieb burgess, christopher: > Stefan, > Look at one of my guests. I can see that: > - ATVHC = serial # of the box > - 3000 = SSID in

Re: Virtual device

2020-10-22 Thread burgess, christopher
Stefan, Look at one of my guests. I can see that: - ATVHC = serial # of the box - 3000 = SSID in array configuration - 0f = unit address in the array configuration Is 000101f4 the zVM specific part? Thanks, Chris Burgess Phone: 1-774-350-9775 Fax: 1-508-544-2076 Email:

Re: Virtual device

2020-10-22 Thread Stefan Haberland
OK, thanks for the complete log. For whatever reason the first path was given a UID without the z/VM specific part. If you call lsdasd -u it should state also only EMC.09000ATVHC.3000.0f for this disk. You may want to try to set the device offline and online again in Linux and see if this

Re: Virtual device

2020-10-22 Thread Stefan Haberland
Am 21.10.20 um 23:25 schrieb Mark Post: > On 10/20/20 11:02 PM, Phil Tully wrote: >> This is SLES12 Sp4 > Hmm. I checked, and the message is the same for that version of the > kernel. If you're sure that is the complete message, and not being > truncated, and the system is running the most recent