>>> On 7/27/2012 at 11:15 AM, Sebastian Ott <seb...@linux.vnet.ibm.com> wrote: > 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.
I believe that's the piece that's missing (for most people). I can easily reproduce the problem on my SLES11 SP2 system with this script: vmcp define vfb-512 302 2000 date +%H:%M:%S.%N chccwdev -e 0.0.0302 mkswap /dev/disk/by-path/ccw-0.0.0302-part1 date +%H:%M:%S.%N udevadm settle chccwdev -d 0.0.0302 vmcp det 302 If fails almost every time. (And if I leave the udevadm settle command out before the chccwdev -d command, that will usually fail also.) If I add a udevadm settle just after the chccwdev -e, it works. Since my system is not heavily loaded, I can't be sure that it will work 100% of the time, but it certainly does a better job than without it. For my SLES10 system, I had to use the udevsettle command, of course. Our dasd_configure script uses udevsettle/udevadm settle for bringing volumes on and offline, and it seems to work fine as well. Mark Post ---------------------------------------------------------------------- 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/
