[Kernel-packages] [Bug 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

2017-09-11 Thread Frank Heimes
** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes 
(frank-heimes)

** Changed in: linux (Ubuntu)
 Assignee: Frank Heimes (frank-heimes) => (unassigned)

** Changed in: ubuntu-z-systems
   Status: Invalid => Won't Fix

-- 
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:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

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:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  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


[Kernel-packages] [Bug 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

2017-09-11 Thread Andrew Cloke
** Changed in: ubuntu-z-systems
   Status: Incomplete => Invalid

-- 
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:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

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:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  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


[Kernel-packages] [Bug 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

2017-06-30 Thread Dimitri John Ledkov
The calls that fail are 'open()' calls. In ubuntu we do not have patches
to s390-tools for dasdfmt code path. Please seek help from s390-tools
upstream developers at IBM.

And call to 'open()' should not require user to have a default shell set
- e.g. it should not be resulting in e.g. system() calls.

Alternatively, please provide steps to reproduce the issue - meaning how
to recreate the z/VM and the un-dasdfmt-able disks.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

-- 
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:
  Incomplete
Status in linux package in Ubuntu:
  Won't Fix

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:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  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


[Kernel-packages] [Bug 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

2016-12-12 Thread Frank Heimes
Indeed, DASDs with a nomenclature of 019* are often for special use, like 0191, 
019D and 019E.
But this is mostly by convention only.
Interesting to know if that applies to this case, too?

-- 
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:
  Incomplete
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:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  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


[Kernel-packages] [Bug 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

2016-11-24 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   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:
  Incomplete
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:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  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


[Kernel-packages] [Bug 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

2016-11-22 Thread Frank Heimes
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
> #1400.0 MBf  ext2  /boot
> #2  6.5 GBf  ext4  /
> #3484.4 MBf  swap  swap
>49.2 kB   unusable
DASD 0.0.0301 (ECKD) - 2.5 GB IBM S390 DASD drive
> #1  2.5 GBf  ext4  /test301 
-
# after installation
ubuntu@hwe0009:~$ lsdasd
Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==
0.0.0200   active  dasda 94:0ECKD  4096   7042MB1802880
0.0.0301   active  dasdb 94:4ECKD  4096   2340MB599040
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:0ECKD  4096   7042MB1802880
0.0.0301   active  dasdb 94:4ECKD  4096   2340MB599040
0.0.0302   active  dasdc 94:8ECKD  4096   2340MB599040
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:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  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:

[Kernel-packages] [Bug 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

2016-11-22 Thread Dimitri John Ledkov
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.75000XG921.9241.00-part1 
/dev/disk/by-id/ccw-IBM.75000XG921.9241.00.181d1854-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.75000XG921.9241.00.85448ae6-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.75000XG921.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:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  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:

[Kernel-packages] [Bug 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

2016-11-21 Thread Dimitri John Ledkov
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:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  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


[Kernel-packages] [Bug 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

2016-11-21 Thread Frank Heimes
May I ask why:
echo 1 > /sys/bus/ccw/devices/0.0.0199/online
was used and not:
chccwdev -e 0.0.0199

Does the usage of chccwdev to set the device only change the situation?

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

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

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:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  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