Bug 2323389 - Fsarchiver v8.5 ships with Fedora 40 but cannot archive and restore a Fedora 40 or Fedora 41 ext4 OS partition.
Summary: Fsarchiver v8.5 ships with Fedora 40 but cannot archive and restore a Fedora ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fsarchiver
Version: 40
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-02 19:26 UTC by ernie_07
Modified: 2025-05-20 20:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-20 20:10:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ernie_07 2024-11-02 19:26:06 UTC
Description of problem:
Fsarchiver v8.5 ships with Fedora 40 but cannot archive and restore a Fedora 40 or Fedora 41 ext4 OS partition.

Version-Release number of selected component (if applicable): fsarchiver version 8.5

How reproducible: 

Steps to Reproduce:
Attempt to Create an archive of a Fedora 40 or Fedora 41 ext4 OS partition.

Actual results:
fsarchiver throws an error related to ext4 incompatibility.
The ext4 filesystem update in Fedora 39 is foundational to this problem.

Expected results:
Normal archive creation.

Additional info:
GPT UEFI environment.
Fsarchiver v8.5 can be used to successfully archive and restore a Fedora 37 - 38 ext4 OS partition.

FYI

Archiving a Fedora 40 ext4 OS partition via systemrescueCD v11.1/fsarchiver v8.7 appears to work but does not correctly create a grub2 bootable partition. After restoring to a different partition and changing the UUID of the original partition to avoid duplicate UUID problems, grub errors on boot with an indication similar to the one that occurs if the desired partition UUID cannot be found

Comment 1 Aoife Moloney 2025-04-28 15:21:30 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
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 '40'.

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 40 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 2 Aoife Moloney 2025-05-20 20:10:06 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 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.