[LU-9470] sanityn test_39a: mtime (1493860882) changed (to 1493860883) on rename Created: 08/May/17  Updated: 03/Jun/17  Resolved: 03/Jun/17

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.10.0
Fix Version/s: Lustre 2.10.0

Type: Bug Priority: Major
Reporter: James Casper Assignee: Niu Yawei (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

onyx-37, full
servers: SLES12.2, master branch, v2.9.56.11, b3565, ldiskfs
clients: SLES12.2, master branch, v2.9.56.11, b3565


Issue Links:
Related
is related to LU-6366 sanityn test_39a: mtime (1426255087) ... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

https://testing.hpdd.intel.com/test_sessions/b7669e10-d1f4-42ce-a573-31dd57859317

Looks identical to LU-6366.

This was seen with an SLES12.2+SLES12.2 config (server+client), but not with EL7+SLES12.2 (server+client).

From test_log:

CMD: onyx-37vm5 touch /mnt/lustre/f39a.sanityn
CMD: onyx-37vm5 touch -m -d @1462324882 /mnt/lustre/f39a.sanityn
CMD: onyx-37vm6 stat -c %Y /mnt/lustre/f39a.sanityn
CMD: onyx-37vm5 date +%s
CMD: onyx-37vm5 echo hello >> /mnt/lustre/f39a.sanityn
CMD: onyx-37vm5 date +%s
CMD: onyx-37vm6 stat -c %Y /mnt/lustre/f39a.sanityn
CMD: onyx-37vm5 mv /mnt/lustre/f39a.sanityn /mnt/lustre/f39a.sanityn-1
CMD: onyx-37vm6 stat -c %Y /mnt/lustre/f39a.sanityn-1
 sanityn test_39a: @@@@@@ FAIL: mtime (1493860882) changed (to 1493860883) on rename 
  Trace dump:
  = /usr/lib64/lustre/tests/test-framework.sh:4931:error()
  = /usr/lib64/lustre/tests/sanityn.sh:1287:test_39a()
  = /usr/lib64/lustre/tests/test-framework.sh:5207:run_one()
  = /usr/lib64/lustre/tests/test-framework.sh:5246:run_one_logged()
  = /usr/lib64/lustre/tests/test-framework.sh:5093:run_test()
  = /usr/lib64/lustre/tests/sanityn.sh:1293:main()


 Comments   
Comment by Jian Yu [ 16/May/17 ]

More failure instances on master branch since 2017-05-04:

https://testing.hpdd.intel.com/test_sets/53e244e8-3105-11e7-b0a8-5254006e85c2

https://testing.hpdd.intel.com/test_sets/ef1e9852-3755-11e7-b0a8-5254006e85c2

https://testing.hpdd.intel.com/test_sets/a3392eea-37b2-11e7-b0a8-5254006e85c2

https://testing.hpdd.intel.com/test_sets/a3392eea-37b2-11e7-b0a8-5254006e85c2

Comment by Peter Jones [ 19/May/17 ]

Niu

Are you able to help with this? It's only started appearing in the last couple of weeks

Peter

Comment by Bob Glossman (Inactive) [ 22/May/17 ]

another on master:
https://testing.hpdd.intel.com/test_sets/30478f7e-3dea-11e7-b3f6-5254006e85c2

Comment by Niu Yawei (Inactive) [ 23/May/17 ]

It looks like an old issue but happens more recently, it was reported in LU-6366 as well. I'm trying to look into the log and code to see what happened there.

Comment by Gerrit Updater [ 31/May/17 ]

Niu Yawei (yawei.niu@intel.com) uploaded a new patch: https://review.whamcloud.com/27348
Subject: LU-9470 osc: update timestamps on write only
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 98f16dd4e889b628902af15dc988728ede32699f

Comment by Gerrit Updater [ 03/Jun/17 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/27348/
Subject: LU-9470 osc: update timestamps on write only
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 385c955d968c03acfa3d664764087def07a3e92c

Comment by Peter Jones [ 03/Jun/17 ]

Landed for 2.10

Generated at Sat Feb 10 02:26:29 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.