[Kernel-packages] [Bug 1643527] Comment bridged from LTC Bugzilla

2017-09-11 Thread bugproxy 
--- Comment From heinz-werner_se...@de.ibm.com 2017-09-11 09:06 EDT---
IBM bugzilla status -> closed , not reproducable. If the problem will be 
detected in the future, a new bugzilla should be opened

-- 
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] Comment bridged from LTC Bugzilla

2017-07-05 Thread bugproxy 
--- 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: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] Comment bridged from LTC Bugzilla

2016-12-13 Thread bugproxy 
--- Comment From ofe...@il.ibm.com 2016-12-13 03:49 EDT---
Hi,

all the devices added are Mini DISKs (MDISKs).
they are all teh same.
there is no layout/physical problem with any disk.
simply taking the device offline and back online fixes the problem without any 
external intervention... a reboot also fixes the problem.

the device is not a multipath device and it is ok it is blacklisted.

19D and 19E are CMS formated but are not relevant to the issue at hand.

As i mentioned before this only happens when the device is being added by a 
user with no default shell specified...
when using a bash user the problem does not happen...

I can't explain why this is related but i am getting persistent results
when changing the users default shell...

I hope this answers all your questions...

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

Re: [Kernel-packages] [Bug 1643527] Comment bridged from LTC Bugzilla

2016-11-27 Thread Dimitri John Ledkov 
On 27 November 2016 at 06:29, bugproxy  wrote:

> --- Comment From ofe...@il.ibm.com 2016-11-27 01:26 EDT---
> Hi,
>
> at the moment i am forced to bring devices online and make them
> persistent in 2 phases... I am aware of chzdev being able to do both.
> thank you for that.
>
> i understand why LVM is preventing my dasdfmt... that is fine. i missed
> that.
>
> the general case is when i get back  "No such device" although i have
> varied the device online, it is visible in lsdasd and i have used
> udevadm settle.
>
> this behavior was consistent for me. it always failed...
>
> as i mentioned in comment 15, the user i was using was created without a
> specific shell... causing it to use the default shell...
>
>
So does that mean exec calls from dasdfmt that failed becuase the user
account has no (typical) shell specified?
As in, is there something that can be improved in the s390-tools source
code to explicitely use /bin/sh for example to mitigate this?

changing the user to run with bash worked around the issue. so i have my
> workaround...  this solved the problem for me and i am fine with this
> solution.
>
> with that said... you can dig further about 19a in the sosreport... you
> will see that i did brought 19a online (only not using chzdev).
> that should be a valid and supported scenario... i think you should check
> that...
>
>
Horum, I am pondering how can the route cuase be further debuged for this
one. This is still reproducible, after the user has a shell set, right?


> thanks!
>
> --
> You received this bug notification because you are a member of Skipper
> Bug Screeners, which is a bug assignee.
> 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"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-z-systems/+bug/1643527/+subscriptions
>


-- 
Regards,

Dimitri.

-- 
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] Comment bridged from LTC Bugzilla

2016-11-26 Thread bugproxy 
--- Comment From ofe...@il.ibm.com 2016-11-27 01:26 EDT---
Hi,

at the moment i am forced to bring devices online and make them
persistent in 2 phases... I am aware of chzdev being able to do both.
thank you for that.

i understand why LVM is preventing my dasdfmt... that is fine. i missed
that.

the general case is when i get back  "No such device" although i have
varied the device online, it is visible in lsdasd and i have used
udevadm settle.

this behavior was consistent for me. it always failed...

as i mentioned in comment 15, the user i was using was created without a
specific shell... causing it to use the default shell...

changing the user to run with bash worked around the issue. so i have my
workaround...  this solved the problem for me and i am fine with this
solution.

with that said... you can dig further about 19a in the sosreport... you will 
see that i did brought 19a online (only not using chzdev).
that should be a valid and supported scenario... i think you should check 
that...

thanks!

-- 
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] Comment bridged from LTC Bugzilla

2016-11-24 Thread bugproxy 
--- Comment From ofe...@il.ibm.com 2016-11-24 08:44 EDT---
found a workaround to this issue.
the user i was using didn't have a shell specified in /etc/passwd.
changing the user to use /bin/bash as the shell worked around the issue.

-- 
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] Comment bridged from LTC Bugzilla

2016-11-21 Thread bugproxy 
--- Comment From ofe...@il.ibm.com 2016-11-22 01:45 EDT---
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!

all the details should be in the sosreport and dbginfo.

-- 
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] Comment bridged from LTC Bugzilla

2016-11-21 Thread bugproxy 
--- Comment From ofe...@il.ibm.com 2016-11-22 01:36 EDT---
just to mention that this is indeed automated code...
We are using chzdev on Ubuntu to make the device persistent using the following 
command:
/sbin/chzdev dasd-eckd 0199 -e -p

you suggested we should use this command instead of:
echo 1 > /sys/bus/ccw/devices/0.0.0199/online

i guess you meant chccwdev -e...

We have no problem changing the code to use chccwdev  instead of the echo.
other distros are not relevant i only mentioned them because you asked why we 
use the echo command. we can run whatever is needed on Ubuntu regardless of 
other distros.

we are using udevadm to settle after the device is linked. we did not
settle after the device was brought online.

please ignore the full path for each command... that is generated
dynamically by the code. the command path will change dynamically if the
command is moved in the future... this is done to overcome cases where
the command is not in the PATH.

Now, for the problem itself...
i changed the code to use chccwdev -e to vary the device online.
i changed the code to also settle after the device is varied online.

i am getting:
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

I have uploaded a new sosreport and dbginfo for you to review.

-- 
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] Comment bridged from LTC Bugzilla

2016-11-21 Thread bugproxy 
--- Comment From ofe...@il.ibm.com 2016-11-21 08:18 EDT---
we are using the echo method because the code is generic to support different 
distributions in different releases...
this is the common way to do it on all of them.
I will test if chccwdev works around the issue and update later...
please keep investigating in the meanwhile...

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