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
mkbackup and mkrescue failing with nvme disks #1928
Comments
|
@perlvan Please give some more details about your RAID layout. Are you using Oracle ASM? |
Yes, we use Oracle ASM. For some reasons i can't attach the logs.. Pasting the snippets of the log..
lsblk:
|
@perlvan could you also paste the output of |
@perlvan sorry we will close this issue without further input in the coming weeks |
Yes please. Thank you.
…Sent from my iPhone
On 27 Dec 2018, at 4:57 PM, gdha ***@***.***> wrote:
@perlvan sorry we will close this issue without further input in the coming weeks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
Relax-and-Recover 2.4 / 2018-06-21
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
BareMetal
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; bootloader GRUB
Storage (lokal disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
NVMe with software RAID (1-mirroring)
Description of the issue (ideally so that others can reproduce it):
Work-around, if any:
The text was updated successfully, but these errors were encountered: