[LU-13687] interop: "lfs find" prints spurious "No such file or directory" error messages

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.14.0, Lustre 2.12.6
• Affects Version/s: Lustre 2.14.0, Lustre 2.12.4
• Environment: v2_13_54-44-gf3fef81
• Assignee: Andreas Dilger
• Reporter: Andreas Dilger

Description

When running "lfs find" it prints a spurious error message for each directory that it processes, and then appears to take the last argument "0" as the directory name when printing the summary error message:

# lfs find /myth/tmp -size +100K --ost 0
lfs find: warning: /myth/tmp does not exist: No such file or directory (2)  
lfs find: warning: /myth/tmp/mythtv does not exist: No such file or directory (2)
lfs find: warning: /myth/tmp/testdir does not exist: No such file or directory (2)
/myth/tmp/pflfile2
/myth/tmp/40T
:
:
error: find failed for 0.

Reversing the order of the arguments prints the final error message correctly:

# lfs find -size +100K --ost 0 /myth/tmp
lfs find: warning: /myth/tmp does not exist: No such file or directory (2)  
lfs find: warning: /myth/tmp/mythtv does not exist: No such file or directory (2)
lfs find: warning: /myth/tmp/testdir does not exist: No such file or directory (2)
/myth/tmp/pflfile2
/myth/tmp/40T
:
:
error: find failed for /myth/tmp.

I suspect the "No such file or directory (2)" message may be incorrectly a result of getxattr() or IOC_MDC_GETFILEINFO on the file returning -ENOENT and that being printed rather than ignored?

Issue Links

• is related to: LU-11656 "lfs getstripe" on directory does not show default root layout