[LU-16944] lfs find: incomplete results when multiple paths precede negated expression Created: 05/Jul/23 Updated: 19/Jul/23 Resolved: 19/Jul/23 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.16.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Thomas Bertschinger | Assignee: | Thomas Bertschinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
When lfs find is used with multiple paths, the final path is not searched if the first option following that path is a ! or an option without an argument, like print:
$ mkdir /mnt/lustre/{a,b}
$ touch /mnt/lustre/{a,b}/f
$ lfs find /mnt/lustre/{a,b} ! -type d
/mnt/lustre/a/f
$ lfs find /mnt/lustre/{a,b} -print
/mnt/lustre/a
/mnt/lustre/a/f
|
| Comments |
| Comment by Gerrit Updater [ 05/Jul/23 ] |
|
"Thomas Bertschinger <bertschinger@lanl.gov>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/51578 |
| Comment by Gerrit Updater [ 19/Jul/23 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/51578/ |
| Comment by Peter Jones [ 19/Jul/23 ] |
|
Landed for 2.16 |