Why find command using almost 100% of disk IO?












0














I forgot when exactly it started, If I am correct that was when I update all packages last week.
On iotop the command is find . -daystart -name NoSuchFile, I dont know what it does to the files it reading, when I tried to use fatrace it open a lot of files per second.



Also SELinux keeps telling about this SELinux is preventing find from open access on the directory /sys/kernel/config. and some read access on irq, dev, usermodehelper, net, rpc, and pcp.WXW8e2p7o.



Anyone can give me some light on this and how should I deal it?



Thanks










share|improve this question






















  • This looks like a prank. Have you tried killing the process?
    – Fabby
    1 hour ago
















0














I forgot when exactly it started, If I am correct that was when I update all packages last week.
On iotop the command is find . -daystart -name NoSuchFile, I dont know what it does to the files it reading, when I tried to use fatrace it open a lot of files per second.



Also SELinux keeps telling about this SELinux is preventing find from open access on the directory /sys/kernel/config. and some read access on irq, dev, usermodehelper, net, rpc, and pcp.WXW8e2p7o.



Anyone can give me some light on this and how should I deal it?



Thanks










share|improve this question






















  • This looks like a prank. Have you tried killing the process?
    – Fabby
    1 hour ago














0












0








0







I forgot when exactly it started, If I am correct that was when I update all packages last week.
On iotop the command is find . -daystart -name NoSuchFile, I dont know what it does to the files it reading, when I tried to use fatrace it open a lot of files per second.



Also SELinux keeps telling about this SELinux is preventing find from open access on the directory /sys/kernel/config. and some read access on irq, dev, usermodehelper, net, rpc, and pcp.WXW8e2p7o.



Anyone can give me some light on this and how should I deal it?



Thanks










share|improve this question













I forgot when exactly it started, If I am correct that was when I update all packages last week.
On iotop the command is find . -daystart -name NoSuchFile, I dont know what it does to the files it reading, when I tried to use fatrace it open a lot of files per second.



Also SELinux keeps telling about this SELinux is preventing find from open access on the directory /sys/kernel/config. and some read access on irq, dev, usermodehelper, net, rpc, and pcp.WXW8e2p7o.



Anyone can give me some light on this and how should I deal it?



Thanks







fedora find disk io selinux






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 1 hour ago









zer09

200213




200213












  • This looks like a prank. Have you tried killing the process?
    – Fabby
    1 hour ago


















  • This looks like a prank. Have you tried killing the process?
    – Fabby
    1 hour ago
















This looks like a prank. Have you tried killing the process?
– Fabby
1 hour ago




This looks like a prank. Have you tried killing the process?
– Fabby
1 hour ago















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491050%2fwhy-find-command-using-almost-100-of-disk-io%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491050%2fwhy-find-command-using-almost-100-of-disk-io%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Entries order in /etc/network/interfaces

新発田市

Grub takes very long (several minutes) to open Menu (in Multi-Boot-System)