-
Bug
-
Resolution: Won't Fix
-
P3
-
None
-
9
-
None
We have noted cases where running "find" on solaris on a directory, where another process is concurrently writing files, can cause find to crash. It seems that if a file is deleted after find has discovered it but not gathered all needed information (?), it exits with the following message:
/usr/ccs/bin/find: stat() error $MODIFIED_FILE: No such file or directory
(Apparently, we're not the only ones affected by this: https://community.oracle.com/thread/1909140?start=0&tstart=0)
I'm thinking three ways to address this, in order of preference:
1) Check if there are Solaris patches that fixes find
2) Check if we can include GNU find in the solaris devkits
3) Write a wrapper around find that catches failures and retries a reasonable number of times, hoping that any failure is unlikely and intermittent.
/usr/ccs/bin/find: stat() error $MODIFIED_FILE: No such file or directory
(Apparently, we're not the only ones affected by this: https://community.oracle.com/thread/1909140?start=0&tstart=0)
I'm thinking three ways to address this, in order of preference:
1) Check if there are Solaris patches that fixes find
2) Check if we can include GNU find in the solaris devkits
3) Write a wrapper around find that catches failures and retries a reasonable number of times, hoping that any failure is unlikely and intermittent.
- relates to
-
JDK-8153273 Test lib compilations trigger find crash on Solaris
-
- Resolved
-
-
JDK-8153281 Workaround another find crash in tonga build
-
- Resolved
-
- links to