Red Hat Bugzilla – Bug 161424
Updating selinux-policy-targeted very slow with large nfs mounts
Last modified: 2007-11-30 17:11:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.8) Gecko/20050512 Firefox/1.0.4
Description of problem:
Updating selinux-policy-targeted on a system with large nfs mounts is very slow. This seems to be because the "find" command in the /sbin/fixfiles script can end up traversing the full directory tree of nfs mounts, even though it doesn't print any of the files they contain, and if the nfs file systems are large this can take a very long time. Replacing the find command with
find $pattern -fstype nfs -prune -o ...
would make things a lot quicker on such systems.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. update selinux-policy-targeted on a system with large nfs mounts
Can you check out the fixfiles from policycoreutils-1.23.18-1
in Rawhide. Would this satisfy you need?
Do you really mean policycoreutils-1.23.18-1 as I can't find that version anywhere?
It is available in Rawhide/FC4
You can also download it (policycoreutils-1.23.18-2) from
The rawhide I can see has policycoreutils-1.23.11-3 . Is this what you mean?
Yes, You can look at that one, I just want you to take a look at fixfiles and
see if that would fix your problem.
No, it doesn't. I should have mentioned that since I submitted the bug I have
seen the problem in FC4 as well. We have an automount at /usr/local and the
sub-mount that contains the fedora patches also contains some unpackaged solaris
patch clusters, which means a lot of files. So the problem occurs when the
script is processing /usr (though /home could potentially cause similar problems
if people are logged on).
Changing the version to FC4 as it affects FC4 as well as FC3.
Fixed in policycoreutils-1.27.2-1.1
No it isn't fixed.
Created attachment 119368 [details]
Patch to stop following nfs partitions
Ok I finally got my head out of my but and read the first message again, about
How does this patch look to you?
Yes, that patch does seem to fix my problem.