Dear all, >From time to time I am confronted with an weird problem with the s390-tools which is really a PITA.
I have a small script that should simply execute a dasdfmt afterwards a fdasd and finally a mkfs to prepare a new DASD. What happens is that after the dasdmft the fdasd gets sometimes the information that the disk is in use and gives an return code and the script stops. This is results now in a kind of game to serialize those commands. In SLES 11 SP1 I could find a solution that after the dasdfmt I would disable the device (chccwdev -d xxxx) and enable it afterwards. There was a wait of some seconds in between. Looking on the Internet I found a better way to circumvent the fixed waiting time: udevadm settle --timeout=60 --exit-if-exists=/dev/dasd would wait till either there is a timeout or the device shows up in the /dev filesystem. Under SP2 I am facing again the problem since either a chccwdev -d xxxx brings now a device busy and delivers a return code or the fdasd returns that the device is busy. Is there a way to safely check if the device is not busy any more? That device is LINKED with W exclusively to the guest executing my script. There is also no other activity on that specific device on this guest. I have the feeling that a new kernel brings sometimes back these troubles. Is there a proper way to address this problem? Thank you very much in advance. -- Best regards Florian Bilek ---------------------------------------------------------------------- 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/
