Bug 1183264

Summary: restore fails to restore incremental dump if a directory was removed
Product: Red Hat Enterprise Linux 7 Reporter: Damien Gombault <desintegr>
Component: dumpAssignee: Josef Ridky <jridky>
Status: CLOSED ERRATA QA Contact: Jan Blazek <jblazek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: j, ovasik
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dump-0.4-0.23.b44.el7 Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 10:02:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1191020, 1295396, 1465925    

Description Damien Gombault 2015-01-17 22:14:52 UTC
Hi.

dump in RHEL 7.0 is affected by a severe bug :
restore fails to restore incremental dump if a directory was removed.
This bug is also present in Fedora 20 and 21.

An upstream patch is available.

Reported and fixed in Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714234
Reported but not fixed in Fedora 18 : https://bugzilla.redhat.com/show_bug.cgi?id=972370
Reported upstream, patch available : http://sourceforge.net/p/dump/bugs/157/

Comment 2 Petr Hracek 2015-02-13 08:39:08 UTC
I will prepare the patch so that in the future we can easily release this Bugzilla.

Comment 4 Damien Gombault 2015-09-16 10:56:42 UTC
Hi.

Is there any progress on this bug ?
Will the patch be included in RHEL 7.2 ?

Comment 5 Petr Hracek 2015-09-16 11:34:08 UTC
AFAIK now. It is not planned.
But I can prepare a BZ. But I guess that it is not planned to updated.
I have set a flag to RHEL-7.3.

Comment 7 Josef Ridky 2016-10-04 08:33:15 UTC
Change flag to rhel-7.4.

Comment 14 errata-xmlrpc 2018-04-10 10:02:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0687