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

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

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

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

[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

[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

[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

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

[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