Bug 2152393 - dump restores a qcows drive as a blank drive
Summary: dump restores a qcows drive as a blank drive
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dump
Version: 37
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jeff Makey
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-11 13:18 UTC by Todd
Modified: 2023-12-06 11:41 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-12-06 11:41:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
restored qcow2 drive seen by gparted (43.42 KB, image/png)
2022-12-11 13:18 UTC, Todd
no flags Details

Description Todd 2022-12-11 13:18:47 UTC
Created attachment 1931788 [details]
restored qcow2 drive seen by gparted

Fedora 36 and 37
dump-0.4-0.49.b47.fc36.x86_64

I have an absolute disaster on my hands.  Dump does not properly restoring my qemu-kvm qcows2 drives.  This is a change from Fedora 35 where I frequently restored my qcows2 drive after goofing my Windows Virtual Machines' (VM's) with updates (have to simulate what my customers see). All VM were off during the dump backup.

I will attach what gparted sees (booting the VM off a live iso).  Basically, the restored drive comes back a blank drive

In the following, the qcows2 file whit the date on the end is the good file.  The one without the date is the restored file:

# ls -al KVM-W11.qcow2 KVM-W11.qcow2_2022-12-11
-rw-r--r--. 1 qemu qemu 33615708160 Dec  8 02:28 KVM-W11.qcow2
-rw-r--r--. 1 qemu qemu 33615708160 Dec  8 02:28 KVM-W11.qcow2_2022-12-11

# sha256sum KVM-W11.qcow2 KVM-W11.qcow2_2022-12-11
2ed61cdbb654c5a6c69200d5531a5147653561c13f75944fb1086d9c80fcd96b  KVM-W11.qcow2
05c48a0994a8c6f748e218104c7a6fd9117b4de357a97c51704ed74082c26f04  KVM-W11.qcow2_2022-12-11

As you can see, they are the same size but not the same contents!

This was the restore command:
# restore -if /lin-bak/2022-12-10_rootExt4Dump.gz

If this does not get fixed, it is going to screw me big time!

Comment 1 Todd 2022-12-11 22:37:20 UTC
I should point out that my qcows2 files are "Sparse"

Comment 2 Aoife Moloney 2023-11-23 00:44:49 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
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
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Aoife Moloney 2023-12-06 11:41:36 UTC
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.