Version-Release number of selected component: mdadm-4.1-rc2.0.2.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/sbin/mdadm --detail --export /dev/md124p2 crash_function: strcpy executable: /usr/sbin/mdadm journald_cursor: s=8a4d27742f7d42208b97828b6b563b75;i=91887;b=f355da85e7f34548b8525ca9c99428e0;m=85fd3d30;t=58776e7736b7c;x=a64959ce575d0210 kernel: 5.0.9-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #2 strcpy at /usr/include/bits/string_fortified.h:90 #3 super_by_fd at util.c:1285 #4 Detail at Detail.c:102 #5 misc_list at mdadm.c:1951 Potential duplicate: bug 1157774
Created attachment 1559521 [details] File: backtrace
Created attachment 1559522 [details] File: cgroup
Created attachment 1559523 [details] File: core_backtrace
Created attachment 1559524 [details] File: cpuinfo
Created attachment 1559525 [details] File: dso_list
Created attachment 1559526 [details] File: environ
Created attachment 1559527 [details] File: limits
Created attachment 1559528 [details] File: maps
Created attachment 1559529 [details] File: mdstat_data
Created attachment 1559530 [details] File: mountinfo
Created attachment 1559531 [details] File: open_fds
Created attachment 1559532 [details] File: proc_pid_status
Created attachment 1559533 [details] File: exploitable
Hi Gerasim I don't reproduce this problem. These are the steps I did: mdadm -CR /dev/md0 -l0 -n2 /dev/nvme0n1p1 /dev/nvme0n1p2 [root@dell-per820-02 ~]# mdadm --detail --export /dev/md0 MD_LEVEL=raid0 MD_DEVICES=2 MD_METADATA=1.2 MD_UUID=b2492d81:cdde663e:1df046bf:4bf0bec3 MD_NAME=0 MD_DEVICE_ev_nvme0n1p1_ROLE=0 MD_DEVICE_ev_nvme0n1p1_DEV=/dev/nvme0n1p1 MD_DEVICE_ev_nvme0n1p2_ROLE=1 MD_DEVICE_ev_nvme0n1p2_DEV=/dev/nvme0n1p2 [root@dell-per820-02 ~]# uname -r 5.0.10-200.fc29.x86_64 [root@dell-per820-02 ~]# cat /etc/redhat-release Fedora release 29 (Twenty Nine) [root@dell-per820-02 ~]# rpm -qa | grep mdadm mdadm-4.1-rc2.0.2.fc29.x86_64 You need to give the commands that can reproduce this problem. Thanks Xiao
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Hi Xiao I can’t say exactly what was the reason and what commands I entered. Fedora 29 eol & i can`t install it.