------- Comment From jan.hoepp...@de.ibm.com 2017-07-05 04:29 EDT-------
Hi Ofer Baruch,

is this issue still relevant and can you still reproduce it?
If this is the case, can you please provide us with some detailed information 
on how
you reproduce it. If you've got a script that is been used, you may provide that
as well.

I already had a look at the dbginfo data but I can't see any of the commands
that you used to trigger the issue. When did you collect the dbginfo data?
If possible, please run dbginfo after you reproduced the issue.

Furthermore, the workaround with the user shell seems a bit odd and makes me
curious. Can you elaborate on that? How did you create the user in the first 
place (when
he had no shell yet) and how is the access to /sbin managed for this user? 
(sudo?)

Thanks a lot and best regards,
Jan

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