sha256deep stopped with futex

[jodkalemon]

I ran two instances of sha256deep -rl on two different directories. Both stopped (do nothing, still running) after 327.900 hashed files. find ./ -type f|wc -l gives more than 700.000 files. strace gives futex(0x7f582a86397c, FUTEX_WAIT_PRIVATE, 592823, NULL and futex(0x7fb5cb5ec97c, FUTEX_WAIT_PRIVATE, 568517, NULL

Interesting fact is: Although the two instances hashed the files in different order, at halt, they both have hashed the exact same files. Looks like the thread which chooses the files to hash stopped or crashed or did something strange.

[ethus3h]

I vaguely remember running into something like this. I think I worked around / fixed it by adding an -o fbsd argument, which tells it to skip character devices, pipes, symlinks, (and possibly Windows executables?? I don't understand the manpage about them.)

       -o <bcpflsd>
              Enables  expert  mode.  Allows the user specify which (and only which) types of files are pro‐
              cessed. Directory processing is still controlled with the -r flag.  The  expert  mode  options
              allowed are:
              f - Regular files
              b - Block Devices
              c - Character Devices
              p - Named Pipes
              l - Symbolic Links
              s - Sockets
              d - Solaris Doors
              e - Windows PE executables