This issue was created by maloo for Andreas Dilger <adilger@thelustrecollective.com>

This issue relates to the following test suite run:
https://testing.whamcloud.com/test_sets/0109704a-3fe0-446d-bb20-682162328694

test_56ob failed with the following error:

'/usr/bin/lfs find /mnt/lustre/d56ob.sanity -mtime 2w' wrong: found 0, expected 1

Test session details:
clients: https://build.whamcloud.com/job/lustre-reviews/123340 - 5.14.0-503.40.1.el9_5.aarch64+64k
servers: https://build.whamcloud.com/job/lustre-reviews/123340 - 4.18.0-553.89.1.el8_lustre.x86_64

This is failing several times per week, with different time ranges (e.g. -mtime 1d, -mtime 4h, -mtime -1y) so it doesn't appear to be a small race with the timestamps, but something more fundamental like not finding files at all, or the timestamps not being set correctly.  The problem happens exclusively on aarch64 or aarch64+64k clients.  There are some other failures of test_56ob on x86_64 clients but they are caused by unrelated problems in the patches being tested (errors creating files or setting timestamps).

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_56ob - '/usr/bin/lfs find /mnt/lustre/d56ob.sanity -mtime 2w' wrong: found 0, expected 1