** 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 t
** 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 me
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() cal
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 l
About 019a.
Nov 22 07:13:46 JUUB16MS kernel: [ 73.806642] dasd-eckd 0.0.019a: A channel
path to the device has become operational
Nov 22 07:13:46 JUUB16MS kernel: [ 73.808080] dasd-eckd 0.0.019a: New DASD
3390/0C (CU 3990/01) with 1443 cylinders, 15 heads, 224 sectors
Nov 22 07:13:46 JUUB16M
** 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 messag
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
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 forc
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
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
10 matches
Mail list logo