[bug #51345] find shows different results despite using same command

[cyrus]

Follow-up Comment #2, bug #51345 (project findutils):

I thought the explanations should be enough. To clarify the problem I
re-explain what happens:
I turn on my Linux machine which has Debian 8 x64 (unstable- kernel 4.9)
installed on it. I run the command 
> #find . -name "*systemd-resolved*" 
and get this output:

./usr/share/man/man8/systemd-resolved.service.8.gz
./usr/share/man/man8/systemd-resolved.8.gz

I run the SAME command for the second time and get this output:

./usr/share/man/man8/systemd-resolved.service.8.gz
./usr/share/man/man8/systemd-resolved.8.gz
./lib/systemd/systemd-resolved
./lib/systemd/system/systemd-resolved.service.d
./lib/systemd/system/systemd-resolved.service

File system is ext4 and ALL the files exist there and are accessible before
running the commands. Now after rebooting this system the same thing happens
exactly like what I said.

I turn on another system with Debian x64 kernel 4.9 which is installed as a
virtual machine. 
Running the same command I get another wrong result. But this time instead of
two lines, the output is empty. 

(Download strace log of first run: https://ufile.io/yjluf)

I run the command for the second time and get correct result:

./usr/share/man/man8/systemd-resolved.service.8.gz
./usr/share/man/man8/systemd-resolved.8.gz
./lib/systemd/systemd-resolved
./lib/systemd/system/systemd-resolved.service.d
./lib/systemd/system/systemd-resolved.service

(Download strace log of second log: https://ufile.io/zweyz)

This all happens after rebooting the second machine too: Wrong output for the
first run.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51345>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/