find utility always starts in "D" state and may keep beeing in this state for as long as it wants(needs?). Could someone explain why. What I am doing is:
# find /(anything) -name ^regExpr(also might be a name*)
sometimes complemented with the "-d" option

Cpu(s): 3.0%us, 2.5%sy, 0.0%ni, 94.2%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
random ss of the top's cpu(s) during this "hang".

Also, the "1min load average" jumps from almost insignificantly to like 5.0. What is it waiting for? Why? My CPU doesn't let it be executed, no idea. Sorry if stupid.

D stands for "Uninterruptible sleep" and running your find under 'strace' should show you why it doesn't work the way you think it should. That said, when looking at '/' you may almost always want "-xdev" because you most likely don't want to recurse into VFS like /proc or /sys and stay on the local system. And maybe my 'find' is old but when I want to search for files with a path-based regex I use "-regex", not "-name" though you can mix 'em NP.

1 members found this post helpful.

If you use find a lot you might be better off using updatedb/locate.

As to why it drops into state "D", that is because most of the time that process will be waiting on (disk) I/O. The spike in loadavg is most likely because other processes doing I/O are being forced to wait as well. Try the following to see if this is true

1 members found this post helpful.

Thank you, guys. Very helpful.