[LU-8493] Do not set stale flag for new created OSP object Created: 10/Aug/16  Updated: 10/Jul/17  Resolved: 22/Aug/16

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

Type: Bug Priority: Major
Reporter: Di Wang Assignee: Di Wang
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
is related to LU-8472 sanity-scrub test_5 times out Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

Do not set stale flags for new created OSP object, otherwise it will cause the following write operation to return ESTALE, especially when cancelling the update record. 

[112275.488838] LustreError: 82035:0:(llog_cat.c:744:llog_cat_cancel_records()) lustre-MDT0000-osp-MDT0001: fail to cancel 1 of 1 llog-records: rc = -116
[112275.489841] LustreError: 82035:0:(update_trans.c:1307:distribute_txn_cancel_records()) lustre-MDT0000-osp-MDT0001: batchid 1 cancel update log 0x2:1025.1 : rc = -116
[112275.491873] LustreError: 82035:0:(update_trans.c:1307:distribute_txn_cancel_records()) lustre-MDT0001-osd: batchid 1 cancel update log 0x2:1073742848.1 : rc = 0

This problem seems brought in by patch http://review.whamcloud.com/19041 LU-7660,
so it only needs to be fixed in 2.9

 Comments   
Comment by Gerrit Updater [ 10/Aug/16 ]

wangdi (di.wang@intel.com) uploaded a new patch: http://review.whamcloud.com/21861
Subject: LU-8493 osp: Do not set stale for new osp obj
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: c3db109202f3d5f3495f7ea09a2defe61a5d41c9

Comment by Gerrit Updater [ 22/Aug/16 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/21861/
Subject: LU-8493 osp: Do not set stale for new osp obj
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 431f18c87d28b7cdfa2c411f5e9e067592254610

Comment by Peter Jones [ 22/Aug/16 ]

Landed for 2.9

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