>Once the DASD driver finished > its work and created a block device, userspace is informed about this via > uevents. After that chccwdev returns. The only thing that's missing now is > udev creating a device node and that's covered via udev settle.
Thanks for the walkthrough. The problem appears to be somewhere after the exit from udev settle -- the device is not always actually ready and available for use when udev settle exits. We're seeing the problem on RHEL 6 guests on varying hardware (zPDT, older Sharks, etc) -- basically slower hardware that can't necessarily respond instantly to requests. I don't know what Florian has, but that seems to be characteristic of what we're seeing when it fails. >So unless I'm missing something the described method > should work reliable on current distros. (In a real world scenario you have to > check return codes of the previous steps before executing the next one.) Yeah. We're getting rc=0 for the chccwdev and udev settle, which is what's kinda weird about it. I'll see if we can convince udev to wait a bit longer on the settle. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] 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/
