[LU-13314] sanity test_56ob: lfs find /mnt/lustre/d56ob.sanity -mtime 1y' wrong: found 0, expected 1 Created: 01/Mar/20 Updated: 18/Feb/21 Resolved: 01/Sep/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | Andreas Dilger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
This issue was created by maloo for Andreas Dilger <adilger@whamcloud.com> This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/0e2fc3d7-0b4f-469a-8b96-7b6fa53e6261 test_56ob failed with the following error: '/usr/bin/lfs find /mnt/lustre/d56ob.sanity -mtime 1y' wrong: found 0, expected 1 This is failing 100% since last night after the most recent master-next landing. VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV |
| Comments |
| Comment by Andreas Dilger [ 02/Mar/20 ] |
|
Wang Shilong wrote:
This seems to be correct. It looks like the bug was introduced in patch https://review.whamcloud.com/34367 " |
| Comment by Andreas Dilger [ 02/Mar/20 ] |
|
It looks like time_margin is exactly 24h, so the leap day plus a few seconds for running the test moves the "touch" file out of range. I think it makes sense to have more than a 1-day margin for files 1 year old. I'm not sure what a sensible default would be, but maybe 1d + 1d/year? That would be enough to fix the leap-day issue, and for files 7 years old that would give a margin of 8d, which I think would be totally acceptable margin of error? |
| Comment by Gerrit Updater [ 02/Mar/20 ] |
|
Wang Shilong (wshilong@ddn.com) uploaded a new patch: https://review.whamcloud.com/37767 |
| Comment by Gerrit Updater [ 02/Mar/20 ] |
|
Andreas Dilger (adilger@whamcloud.com) merged in patch https://review.whamcloud.com/37767/ |
| Comment by Mikhail Pershin [ 02/Mar/20 ] |
|
this is lfs calc error in set_time(). It uses 365 days in year always, so to work correctly is should takes leap day into account while doing maths for +/- year/week |
| Comment by Gerrit Updater [ 17/Jul/20 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/39433 |
| Comment by Andreas Dilger [ 17/Jul/20 ] |
|
I fixed this by increasing the margin of error by a day per year. I have a follow-on patch that will allow searching between precise intervals (e.g. "-atime +30 -atime -60" that needs to be finished, but at least this first patch/test is functional again. |
| Comment by Gerrit Updater [ 12/Aug/20 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/39657 |
| Comment by Gerrit Updater [ 01/Sep/20 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/39433/ |
| Comment by Peter Jones [ 01/Sep/20 ] |
|
Landed for 2.14 |