I tried to re-create the situation over here.

I have a z/VM 6.4:
q cplevel
z/VM Version 6 Release 4.0, service level 1901 (64-bit)
Generated at 06/14/19 14:15:49 UTC

and there is a VM guest running from the time I did 18.04.4 regression testing, 
hence it's up since quite some time:
buntu@zbox:~$ uptime
 05:16:47 up 36 days, 22:17,  1 user,  load average: 0.00, 0.00, 0.00
but has an older kernel:
ubuntu@zbox:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.4 LTS
Release:        18.04
Codename:       bionic
ubuntu@zbox:~$ uname -a
Linux zbox 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:23:44 UTC 2020 s390x 
s390x s390x GNU/Linux
ubuntu@zbox:~$ 

It has 4 FBA devices:
$ lszdev | grep yes
dasd-eckd    0.0.0200                    yes  yes   dasda
dasd-fba     0.0.0101                    yes  yes   dasdc
dasd-fba     0.0.0102                    yes  yes   dasdb
dasd-fba     0.0.0103                    yes  yes   dasdd
dasd-fba     0.0.0104                    yes  yes   dasde
qeth         0.0.0600:0.0.0601:0.0.0602  yes  yes   enc600
generic-ccw  0.0.0009                    yes  yes   

I had a look at the logs (dmesg,syslog) and couldn't find any problems with FBA 
devices:
ubuntu@zbox:~$ dmesg -xT -l emerg,alert,crit,err
ubuntu@zbox:~$ grep 'error\|fail\|crash\|warn\|crit' /var/log/syslog
Mar 12 06:57:46 zbox systemd-resolved[371]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
Mar 12 09:21:16 zbox systemd-resolved[371]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
ubuntu@zbox:~$

So I upgraded the system to the latest package and kernel level:
ubuntu@zbox:~$ sudo apt -y -q update && sudo apt -y -q full-upgrade && sudo apt 
autoremove --purge
ubuntu@zbox:~$ lsb_release -r
Release:        18.04
ubuntu@zbox:~$ uname -a
Linux zbox 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:02 UTC 2020 s390x 
s390x s390x GNU/Linux
ubuntu@zbox:~$ 
ubuntu@zbox:~$ dmesg -xT -l emerg,alert,crit,err

And I still cannot find any FBA issues:
ubuntu@zbox:~$ grep 'error\|fail\|crash\|warn\|crit' /var/log/syslog
Mar 12 06:57:46 zbox systemd-resolved[371]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
Mar 12 09:21:16 zbox systemd-resolved[371]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
ubuntu@zbox:~$

You mentioned that things might happen under load, so I created and copied 
files with dd, and ran bonnie++ to create some more disk utilization and even 
ran partially stress-ng in parallel,
but still cannot recreate the FBA issue.


In other words I was not able to recreate the problem. I work on a z13 with a 
DS8870.
What about your system? Did you double checked that there are no issues in the 
environment and the FBA definition?

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

** 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/1867118

Title:
  dasd_fba io error and kernel panic

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Generated I/O errors every hour in syslog and caused kernel panic with 
workloads running
   
  ---uname output---
  Linux ubuntutest01 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:02 UTC 
2020 s390x s390x s390x GNU/Linux
   
  ---Patches Installed---
  distro provided. up-to-date from Ubuntu18.04.
   
  Machine Type = z15 
   
  ---System Hang---
   The hourly generated I/O errors didn't impact the system up and running. 
When there are workloads on it, it will cause kernel panic and rebooted the 
server. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   After migrated from 16.04 to 18.04, will see the i/o errors. 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
    The system is not configured to capture a system dump.
   
  Device driver error code:
   [52297.898232] dasd.5c0c98: 0.0.0100: default ERP has run out of retries and 
failed
  [52297.898244] dasd(fba): I/O status report for device 0.0.0100:
                 dasd(fba): in req: 000000002e142bcd CS: 0x20 DS: 0x0C
                 dasd(fba): device 0.0.0100: Failing CCW: 00000000a84f6c9f
                 dasd(fba): SORRY - NO VALID SENSE AVAILABLE
  [52297.898255] dasd(fba): Related CP in req: 000000002e142bcd
                 dasd(fba): CCW 00000000d15f44d3: 63400010 7FE2BBA0 DAT: 
00000200 008150F2 00000000 00000017
                 dasd(fba): CCW 00000000b09ad76e: 43400008 7FE2BBB0 DAT: 
05000006 00000000
                 dasd(fba): CCW 00000000c44dfb20: 41600C00 F3600000 DAT: 
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
                 dasd(fba): CCW 00000000a84f6c9f: 43400008 7FE2BBB8 DAT: 
05000010 00000006
                 dasd(fba): CCW 0000000022dac88c: 41600000 00000000 DAT:
                 dasd(fba): CCW 0000000069686544: 43400008 7FE2BBC0 DAT: 
05000002 00000016
                 dasd(fba): CCW 000000007bb6a17c: 41200400 F3600000 DAT: 
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
  [52297.898278] print_req_error: I/O error, dev dasda, sector 8474866
   
  *Additional Instructions for y...@cn.ibm.com: 
  -Attach sysctl -a output output to the bug.

  [reply] [?]
  Internal Only
  Comment 1 QI YE 2020-03-12 02:29:20 CDT

  The z/VM version 6.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867118/+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