+++ This bug was initially created as a clone of Bug #576213 +++ +++ This bug was initially created as a clone of Bug #494303 +++ Description of problem: When restoring a file that has the immutable flag set, restore displays a warning (see below) and the SELinux file context is not fully restored. This bug maybe is a regression of bz#208835 , which was filed against Fedora 5. * following warning was issued when restoring /boot files restore: ./config-2.6.18-128.el5PAE: EA set security.selinux:system_u:object_r:boot_t:s0 failed: Operation not permitted * SELinux context before dump was called: -rw-r--r-- root root system_u:object_r:boot_t /boot/config-2.6.18-128.el5PAE * SELinux context after restore was called: -rw-r--r-- root root root:object_r:boot_t /boot/config-2.6.18-128.el5PAE Version-Release number of selected component (if applicable): RHEL5-Server-U3 dump-0.4b41-2.fc6 How reproducible: always Steps to Reproduce: 1. Choose a directory and add immutable flag to one of its files. 2. Create a dump of the directory. 3. Delete all files in the directory. 4. Restore the dump in the same directory. 5. Check immutable flag and SELinux context. Actual results: restore displays a warning when restoring the file with immutable flag set Expected results: restore displays no warnings when restoring the file with immutable flag set --- Additional comment from pm-rhel on 2009-11-06 14:26:42 EST --- This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". --- Additional comment from jgorig on 2010-01-07 09:09:54 EST --- Created an attachment (id=382238) Bug fixed in Fedora Bug fixed in Fedora. Patch attached. --- Additional comment from tsh.ac.uk on 2010-03-23 09:44:44 EDT --- I'm still getting problems like this using dump/restore from the Live FC12. It seems to be using the latest version of dump/restore dump-0.4-0.3.b42.fc12.i686. Does this version incorporate the patch? Cheers, Terry --- Additional comment from atkac on 2010-03-23 10:02:02 EDT --- (In reply to comment #4) > I'm still getting problems like this using dump/restore from the Live FC12. > It seems to be using the latest version of dump/restore > dump-0.4-0.3.b42.fc12.i686. Does this version incorporate the patch? No, because noone reported this issue against Fedora. Patch is applied only in current development branch (Fedora 14). If you would like to get this issue fixed in Fedora 12 & 13 open new ticket, please (click on "Clone This Bug" button in upper right corner and select appropriate product, Fedora 12 in your case).
FYI I also got one of these errors: resync restore, skipped 1 blocks error in EA block 1 magic = 0 discussed here: http://sourceforge.net/tracker/?func=detail&aid=2964667&group_id=1306&atid=101306 Cheers, Terry
*** Bug 576213 has been marked as a duplicate of this bug. ***
dump-0.4-0.4.b42.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/dump-0.4-0.4.b42.fc12
dump-0.4-0.4.b42.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update dump'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/dump-0.4-0.4.b42.fc12
dump-0.4-0.4.b42.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.