so with fresh and clean disks it works - even if using the not
recommended way to use echo for setting the disks online (rather than
the recommended way of using chzdev):

# during installation in d-i
0.0.0200 (configured)
0.0.0301 (configured)     # minidisk 1st part or dasd 2605 mod09
0.0.0302                  # minidisk 2nd part or dasd 2605 mod09
0.0.0303                  # minidisk 2nd part or dasd 2605 mod09
# only the 1st part configured and used during installation, just to verify 
that it works in general
...
# rough sample disk layout
DASD 0.0.0200 (ECKD) - 7.4 GB IBM S390 DASD drive
>     #1    400.0 MB    f  ext2          /boot
>     #2      6.5 GB    f  ext4          /
>     #3    484.4 MB    f  swap          swap
>            49.2 kB       unusable
DASD 0.0.0301 (ECKD) - 2.5 GB IBM S390 DASD drive
>     #1      2.5 GB    f  ext4          /test301 
-
# after installation
ubuntu@hwe0009:~$ lsdasd
Bus-ID     Status      Name      Device  Type  BlkSz  Size      Blocks
==============================================================================
0.0.0200   active      dasda     94:0    ECKD  4096   7042MB    1802880
0.0.0301   active      dasdb     94:4    ECKD  4096   2340MB    599040
ubuntu@hwe0009:~$
-
# other minidisks visible ...
ubuntu@hwe0009:~$ ls -la /sys/bus/ccw/devices/0.0.03*
lrwxrwxrwx 1 root root 0 Nov 22 13:33 /sys/bus/ccw/devices/0.0.0301 -> 
../../../devices/css0/0.0.0002/0.0.0301
lrwxrwxrwx 1 root root 0 Nov 22 13:33 /sys/bus/ccw/devices/0.0.0302 -> 
../../../devices/css0/0.0.0003/0.0.0302
lrwxrwxrwx 1 root root 0 Nov 22 13:33 /sys/bus/ccw/devices/0.0.0303 -> 
../../../devices/css0/0.0.0004/0.0.0303
-
# setting 2nd part aka minidis online
ubuntu@hwe0009:~$ cat /sys/bus/ccw/devices/0.0.0302/online 
0
-
# trial using echo to set device online (even if chzdev is recommended)
root@hwe0009:~# echo 1 > /sys/bus/ccw/devices/0.0.0302/online
root@hwe0009:~# cat /sys/bus/ccw/devices/0.0.0302/online
1
-
# fully enabled disk in Linux using chzdev
root@hwe0009:~# chzdev dasd 0.0.0302 -e
ECKD DASD 0.0.0302 configured
-
# format works w/o any issues
root@hwe0009:~# dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0302 -y
Finished formatting the device.
Rereading the partition table... ok
root@hwe0009:~#
-
# disk is there
root@hwe0009:~# lsdasd 
Bus-ID     Status      Name      Device  Type  BlkSz  Size      Blocks
==============================================================================
0.0.0200   active      dasda     94:0    ECKD  4096   7042MB    1802880
0.0.0301   active      dasdb     94:4    ECKD  4096   2340MB    599040
0.0.0302   active      dasdc     94:8    ECKD  4096   2340MB    599040
root@hwe0009:~#

So this is a '+1' for Dimitris investigations that your issue is
probably caused by the LVM config ...

-- 
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

Reply via email to