--- Comment From heinz-werner_se...@de.ibm.com 2020-12-01 05:26 EDT---
IBM Bugzilla status->closed, Fix Released by all requested distros
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867118
--- Comment From heinz-werner_se...@de.ibm.com 2020-10-23 03:29 EDT---
*** Bug 185933 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867118
--- Comment From y...@cn.ibm.com 2020-10-22 21:30 EDT---
Based on this comments, can I say the issue is fixed in Ubuntu20.04?
(In reply to comment #29)
> The focal part of this ticket is addressed by:
> "Focal update: v5.4.69 upstream stable release"
>
--- Comment From stefan.haberl...@de.ibm.com 2020-10-22 11:52 EDT---
*** Bug 188223 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867118
--- Comment From heinz-werner_se...@de.ibm.com 2020-10-15 03:37 EDT---
@Canonical: Where is this commit currently integrated
commit 709192d531e5 ("s390/dasd: Fix zero write for FBA devices").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
--- Comment From y...@cn.ibm.com 2020-03-13 04:48 EDT---
~# lsdasd -l
0.0.0100/dasda/94:0
status: active
type: FBA
blksz: 512
size: 51200MB
blocks: 104857600
--- Comment From cborn...@de.ibm.com 2020-03-13 03:59 EDT---
Can you collect
lsdasd -l
lsdasd -v
also the complete result of dbginfo.sh (as this contains the debuglog
for the dasd driver)
If you can easily reproduce the issue it might be helpful to increase
the log level, but lets start
--- Comment From y...@cn.ibm.com 2020-03-12 22:51 EDT---
We are running it on z15. We have other distros running on this env with FBA.
We don't see that issue.
Here is an additional info I just found out. If I switch the kernel back
to 4.4.0-174-generic, I don't see those errors anymore.
