When I pass
--color=always to ls, it occasionally outputs a number of
No such file or directory errors, like this:
~/svn/projects/submm/adda/scat$ /bin/ls --color=always ls: cannot access adda_output_f89: No such file or directory ls: cannot access adda_output_f150: No such file or directory ls: cannot access adda_output_f183: No such file or directory ls: cannot access adda_output_f186: No such file or directory ls: cannot access adda_output_f190: No such file or directory ...
Later follow the contents of the directory, including the subdirectory
adda_output_f89 coloured as a directory.
There is a process running that is operating on files in this directory, but I don't think it's doing anything with the directories that
ls is mentioning.
It is not fully reproducible. I have so far not succeeded in finding out a pattern when it happens and when it doesn't happen. It appears to happen in waves. Perhaps a process is rapidly creating and removing directories, but I don't think that's true.
It appears to be happening only when I pass
--color=always, but I am not 100% sure that this is the case. Normally I use an alias,
ls='ls --classify --color=always --human-readable' where it does happen, but when I call
/bin/ls it appears that it does not happen.
ls -i gives for those files:
? adda_output1_f243/ ? adda_output_f243/
This is a nfs filesystem.
What might cause this behaviour? Is it some kind of race condition?