Red Hat Bugzilla – Bug 142525
Selinux extensions create lots of dump errors
Last modified: 2013-07-02 19:03:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Description of problem:
When trying to run dump on an Ext3 filesystem which supports the
selinux ACL extensions I get a ton of errors from dump saying:
DUMP: ACLs in inode #12 won't be dumped
..and this repeats for every inode.
Having discussed this on the fedora mailing list it isn't much of a
problem that the ACLs aren't stored since they can be retrieved with
restorecon, but the volume of errors currently makes dump unusable.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Run dump on an selinux enabled Ext3 filesystem
Actual Results: Lots and lots of errors
Expected Results: Preferably that dump should retain and restore the
extra ACL information, but more realistically in the short term a
single warning in the output that ACLs are not supported rather than a
separate warning for each inode.
I'm putting this down as a high priority since it's actually stopping
us (and presumably others) from running our normal backup routines.
Those are NOT errors but warning messages, which are completly
harmless. If the high amount of warnings bothers you, feel free to
pipe the dump stderr output through 'grep -v "ACLs in inode"' or even
comment out the printf in the sources.
That being said, I am working right now on implementing EA support in
dump (already done) and in restore (much more tricky). I plan on
having an alpha version really soon now, but the changes to restore
are rather intrusive so it will have to go through a beta test period
before including it into the mainline dump.
If you're interested in beta testing, just say so.
BTW, the patch implementing EA support is available now from
Created attachment 108514 [details]
Path to suppress the warnings
Simon, please apply this patch if you want to get rid of these warnings.
Stellian, thanks for the quick response. Moving severity to low as it
doesn't affect functionality of dump.
Just thought I'd add a comment to say that having used the workaround
suggested I've got our backups going again and all seems to be well.
I'll look at the new CVS version next week and report back with any
Many thanks for a quick response to this issue.
In fact you need both the CVS version and the dump-ea patch from:
Resolving NOTABUG as the warning messages are not a bug but a feature.