Ubuntu defaults to using and supporting chzdev. There are no Ubuntu
releases without chzdev. Please ask other distros to ship chzdev for
cross-distro compatibility and support.
If this is being automated inside scripts, one needs to replicate
everything that chzdev does - including waiting for the udev to settle.
I recommend you to do something like this:
if ! chzdev dasd-eckd 0199 -e -p; then
echo 1 > /sys/bus/ccw/devices/0.0.0199/online
fi
Or e.g.:
chzdev dasd-eckd 0199 -e -p || :
echo 1 > /sys/bus/ccw/devices/0.0.0199/online
Such that the default and preffered method to enable the devices is
always attempted and used first, rather than as a fallback. Especially
since all distributions will support chzdev eventually.
Please note, that since many distributions ar emerging sbin & bin, and /
with /usr, encoding full path to chzdev might not be as future proof as
using $PATH look-up.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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
