What I'm trying to ask you, is to only use chzdev. No echos. No chccwdev. As both echo & chccwdev are redundant if one uses chzdev.
chzdev can online the devices, and make that persistent, and wait for udev to settle. Doing all three actions in one go. E.g. $ sudo chzdev -e 0199 The -p flag forces chzdev to skip bringing the device online, and only modify the persistent configuration... Yet from your goals you appear to want to both online it & make that persistent. root@JUUB16MS:~# /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.019a -y /sbin/dasdfmt: Unable to open device /dev/disk/by-path/ccw-0.0.019a: No such device This suggests that device is offline. Has the following command been run?: $ sudo chzdev -e 019a on device 198 and 199 the output is different: /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y Disk in use! Digging further into the sosreport data. The behavior above is expected, as there are physical LVM volumes in use on 199-part1 and 198-part2. Note that upon bringing devices online, the physical volumes, logical groups and volumes are automatically activated. One should use vgchange / vgreduce to deactivate relevant volume groups and make sure that physical volumes on 199-part1 & 198-part2 are not in activate use by active volume groups before reformatting. Please note, in addition to LVM, mdadm software RAID, btrfs and zfs can make devices become in use upon bringing them up online as well thanks to systemd-udevd and/or monitoring agents. S: disk/by-path/ccw-0.0.0199-part1 E: DEVLINKS=/dev/disk/by-id/ccw-IBM.750000000XG921.9241.00-part1 /dev/disk/by-id/ccw-IBM.750000000XG921.9241.00.0000181d000018540000000000000000-part1 /dev/disk/by-id/ccw-0X0199-part1 /dev/disk/by-path/ccw-0.0.0199-part1 /dev/disk/by-id/lvm-pv-uuid-LgRz3a-6rkf-xZt3-FoHb-wCcG-XqgL-clWlWD E: DEVNAME=/dev/dasdh1 E: DEVPATH=/devices/css0/0.0.0011/0.0.0199/block/dasdh/dasdh1 E: DEVTYPE=partition E: ID_BUS=ccw E: ID_FS_TYPE=LVM2_member E: ID_FS_USAGE=raid E: ID_FS_UUID=LgRz3a-6rkf-xZt3-FoHb-wCcG-XqgL-clWlWD E: ID_FS_UUID_ENC=LgRz3a-6rkf-xZt3-FoHb-wCcG-XqgL-clWlWD E: ID_FS_VERSION=LVM2 001 S: disk/by-path/ccw-0.0.0198-part2 E: DEVLINKS=/dev/disk/by-id/ccw-IBM.750000000XG921.9241.00.0000854400008ae60000000000000000-part2 /dev/disk/by-id/ccw-0X0192-part2 /dev/disk/by-id/lvm-pv-uuid-b2Bob7-Evkm-BJTc-S4m3-Xc2E-Lmbu-u9XHhk /dev/disk/by-id/ccw-IBM.750000000XG921.9241.00-part2 /dev/disk/by-path/ccw-0.0.0198-part2 E: DEVNAME=/dev/dasdg2 E: DEVPATH=/devices/css0/0.0.0010/0.0.0198/block/dasdg/dasdg2 E: DEVTYPE=partition E: ID_BUS=ccw E: ID_FS_TYPE=LVM2_member E: ID_FS_USAGE=raid E: ID_FS_UUID=b2Bob7-Evkm-BJTc-S4m3-Xc2E-Lmbu-u9XHhk E: ID_FS_UUID_ENC=b2Bob7-Evkm-BJTc-S4m3-Xc2E-Lmbu-u9XHhk E: ID_FS_VERSION=LVM2 001 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1643527 Title: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported" Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Incomplete Bug description: Problem description: procedure: echo 1 > /sys/bus/ccw/devices/0.0.0199/online /sbin/chzdev dasd-eckd 0199 -e -p /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y dasdfmt fails with: /sbin/dasdfmt: Unable to open device /dev/disk/by-path/ccw-0.0.0199: No such device looking at the syslog i can see a strange message that only comes out when i am having this issue: Nov 21 08:52:12 JUUB16MS kernel: [ 67.412484] dasd-eckd 0.0.0199: The disk layout of the DASD is not supported lsdasd returns: root@JUUB16MS:~# lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks ============================================================================== 0.0.0192 active dasda 94:0 ECKD 4096 5070MB 1298160 0.0.0195 active dasdb 94:4 FBA 512 40MB 81920 0.0.0193 n/f dasdc 94:8 ECKD 0.0.0196 active dasdd 94:12 FBA 512 40MB 81920 0.0.0194 n/f dasde 94:16 ECKD 0.0.0197 n/f dasdf 94:20 ECKD 0.0.0198 n/f dasdg 94:24 ECKD 0.0.0199 n/f dasdh 94:28 ECKD you can see that the 199 is not format and can't be formatted... a workaround is to vary the disk offline and then online again. this time it will start ok and you can format it and work with it. ------------------------------ just to be clear... this happens after linking to an un-formatted disk dynamically and then vary it online... for example: vmcp link '*' 199 199 echo 1 > /sys/bus/ccw/devices/0.0.0199/online /sbin/chzdev dasd-eckd 0199 -e -p /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1643527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
