Public bug reported: == Comment: #0 - Thorsten Diehl <thorsten.di...@de.ibm.com> - 2022-08-16 12:40:46 == I installed Ubuntu 20.04.4 LTS on IBM z14, enabled two DASDs, created one partition on each DASD and created an mvdump.conf file like this: /dev/dasdc1 /dev/dasdd1
I wrote the boot record by zipl -n -M mvdump.conf and IPLed the system from dasdc devno. The dump completed succesfully. Then I tried to get this dump via zgetdump on the restarted Ubuntu 20.04.4 system (zgetdump -v reports version 2.12.0-build-20220506), I got the following error: root@m8330032:~# zgetdump -i /dev/dasdc zgetdump: Could not open "/sys/bus/ccw/devices/0.0.9405/dasdc/dev" (No such file or directory) root@m8330032:~# zgetdump -i /dev/dasdc1 zgetdump: Could not open "/sys/bus/ccw/devices/0.0.9405/dasdc/dev" (No such file or directory) root@m8330032:~# zgetdump -i /dev/dasdd zgetdump: Could not open "/sys/bus/ccw/devices/0.0.9405/dasdc/dev" (No such file or directory) root@m8330032:~# zgetdump -i /dev/dasdd1 zgetdump: No valid dump found on "/dev/dasdd1" root@m8330032:~# However, If I'm doing the same zgetdump on another system (e.g. with newer s390-tools version), I get the expected result m83lp32:~ # zgetdump -i /dev/dasdc General dump info: Dump format........: s390mv_ext Version............: 1 Dump created.......: Tue, 16 Aug 2022 18:31:57 +0200 Dump ended.........: Tue, 16 Aug 2022 18:32:02 +0200 Dump CPU ID........: ff1fa1e739068000 UTS node name......: m8330032.lnxne.boe UTS kernel release.: 5.4.0-124-generic UTS kernel version.: #140-Ubuntu SMP Thu Aug 4 02:23:07 UTC 2022 Build arch.........: s390x (64 bit) System arch........: s390x (64 bit) CPU count (online).: 16 CPU count (real)...: 16 Dump memory range..: 4096 MB Real memory range..: 4096 MB Dump file size.....: 849 MB Memory map: 0000000000000000 - 00000000ffffffff (4096 MB) Dump device info: Volume 0: 0.0.9405 (online/active) Volume 1: 0.0.9406 (online/valid) m83lp32:~ # The error is easily reproducible. Please update zgetdump to a newer version to solve this RAS problem. With Jammy (22.04.1; s390-tools version 2.20.0-build-20220623) this problem does not occur. == Comment: #3 - Jan Hoeppner <jan.hoepp...@de.ibm.com> - 2022-08-22 01:43:45 == There were several issues fixed in s390-tools v2.15.1 in regards to multivolume dumps: https://github.com/ibm-s390-linux/s390-tools/releases/tag/v2.15.1 Especially the following upstream commit for zgetdump: https://github.com/ibm-s390-linux/s390-tools/commit/d55b787d05eb9bd70f93c36cf859b66b2ad02038 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-199411 severity-medium targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-199411 severity-medium targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- 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/1987387 Title: [UBUNTU 20.04] zgetdump can not handle multivolume dumps Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Thorsten Diehl <thorsten.di...@de.ibm.com> - 2022-08-16 12:40:46 == I installed Ubuntu 20.04.4 LTS on IBM z14, enabled two DASDs, created one partition on each DASD and created an mvdump.conf file like this: /dev/dasdc1 /dev/dasdd1 I wrote the boot record by zipl -n -M mvdump.conf and IPLed the system from dasdc devno. The dump completed succesfully. Then I tried to get this dump via zgetdump on the restarted Ubuntu 20.04.4 system (zgetdump -v reports version 2.12.0-build-20220506), I got the following error: root@m8330032:~# zgetdump -i /dev/dasdc zgetdump: Could not open "/sys/bus/ccw/devices/0.0.9405/dasdc/dev" (No such file or directory) root@m8330032:~# zgetdump -i /dev/dasdc1 zgetdump: Could not open "/sys/bus/ccw/devices/0.0.9405/dasdc/dev" (No such file or directory) root@m8330032:~# zgetdump -i /dev/dasdd zgetdump: Could not open "/sys/bus/ccw/devices/0.0.9405/dasdc/dev" (No such file or directory) root@m8330032:~# zgetdump -i /dev/dasdd1 zgetdump: No valid dump found on "/dev/dasdd1" root@m8330032:~# However, If I'm doing the same zgetdump on another system (e.g. with newer s390-tools version), I get the expected result m83lp32:~ # zgetdump -i /dev/dasdc General dump info: Dump format........: s390mv_ext Version............: 1 Dump created.......: Tue, 16 Aug 2022 18:31:57 +0200 Dump ended.........: Tue, 16 Aug 2022 18:32:02 +0200 Dump CPU ID........: ff1fa1e739068000 UTS node name......: m8330032.lnxne.boe UTS kernel release.: 5.4.0-124-generic UTS kernel version.: #140-Ubuntu SMP Thu Aug 4 02:23:07 UTC 2022 Build arch.........: s390x (64 bit) System arch........: s390x (64 bit) CPU count (online).: 16 CPU count (real)...: 16 Dump memory range..: 4096 MB Real memory range..: 4096 MB Dump file size.....: 849 MB Memory map: 0000000000000000 - 00000000ffffffff (4096 MB) Dump device info: Volume 0: 0.0.9405 (online/active) Volume 1: 0.0.9406 (online/valid) m83lp32:~ # The error is easily reproducible. Please update zgetdump to a newer version to solve this RAS problem. With Jammy (22.04.1; s390-tools version 2.20.0-build-20220623) this problem does not occur. == Comment: #3 - Jan Hoeppner <jan.hoepp...@de.ibm.com> - 2022-08-22 01:43:45 == There were several issues fixed in s390-tools v2.15.1 in regards to multivolume dumps: https://github.com/ibm-s390-linux/s390-tools/releases/tag/v2.15.1 Especially the following upstream commit for zgetdump: https://github.com/ibm-s390-linux/s390-tools/commit/d55b787d05eb9bd70f93c36cf859b66b2ad02038 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987387/+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
