New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coredump during rear mkrescue #2273
Comments
@adatum I think for debugging what the root cause is Furthermore in ReaR's log file there are time stamps |
In the debug log from
The system kernel log also shows this segfault message just before the coredump posted previously.
|
@adatum Perhaps it is worthwhile to open a bugzilla report with Fedora31? |
@gdha As far as I know, this coredump happens only with ReaR. What would a bug report with Fedora31 be about? Do you have suggestions on what to try to debug this? The "good" part is the coredump is consistent: it happens every time mkrescue is run. |
@adatum Can you reproduce this behavior outside of rear? If you run |
@gdha Thanks for the follow up. I could not reproduce the coredump with your suggestion. After
|
Perhaps
so perhaps this issue is a similar one as Because "no news is good news" I blindly guess that this issue here |
ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.5-git.3350.aa82834d.unknown / 2019-05-10
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
Fedora 31 MATE
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
PC
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
x86_64
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
UEFI, GRUB
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
local SSD
Description of the issue (ideally so that others can reproduce it):
Since upgrading to Fedora 31, the following coredump messages are found in
journalctl
whenrear mkrescue
is run:Nevertheless:
I am not certain but I think the coredump appears at the point when the verbose output shows:
I tested that the rear image boots in a VM, but I did not test a recovery.
Other potentially unrelated warnings or errors during
rear -v mkrescue
:Again I'm not certain, but I think those messages were coming up before the coredump issue began.
The text was updated successfully, but these errors were encountered: