[LU-16798] lfs find: new --jobid option

• Type: Improvement
• Resolution: Won't Do
• Priority: Minor
• Severity: 3
• Assignee: WC Triage
• Reporter: Thomas Bertschinger

Description

Once the jobid is added to files as an xattr, lfs find should be modified to allow searching on this value.

There can be a --jobid argument, and perhaps a printf directive like "%LJ" as well.

Issue Links

• has to be done after: LU-13031 store JobID of program that created file in inodes at create time
• is related to: LU-18889 "lfs find -printf" optimization
• is related to: LU-15837 "lfs find -printf" improvements
• is related to: LU-15743 "lfs find" is missing "-xattr" support

Comments

[Andreas Dilger]

bertschinger, while I agree that the jobid xattr name could be set arbitrarily, I think in the common case it would either user.job or trusted.job, and as such it would still be a useful convenience option to have a "--jobid XXXX" option was a "convenience" alias that searched for both "--xattr user.job=XXXX" and "--xattr user.job=XXXX" xattr names instead of having to specify this directly on the command line.

The lfs-find.1 man page could document this behavior of "--jobid" and recommend falling back to the --xattr option as needed. Actually, it might be possible for the configuration parameter that sets "job_xattr" on the servers to be copied/renamed to a client parameter name, where it would just be saved in memory to be printed again for exactly this usage.

[Thomas Bertschinger]

Rejecting because the jobid xattr name is being determined via an MDT parameter, thus any user tool that uses the xattr will need to take the xattr name as an argument. This makes this redundant with lfs find --xattr which takes the xattr name as an argument. This option would only be useful if the xattr name could be hardcoded (or automatically queried) from a client utility, which is not currently the case.