[LU-15133] don't deactivate OST upon normal precreate error Created: 20/Oct/21  Updated: 20/Jan/22  Resolved: 06/Jan/22

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

Type: Bug Priority: Minor
Reporter: Lai Siyao Assignee: Lai Siyao
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

If osp_get_lastfid_from_ost() RPC failed, it will deactivate OST to let user to handle bad OST, but there may be different kinds of errors, some may be trivial, e.g. network issue, it's not necessary to deactivate OST in such cases. Among all the errors, -EFAULT means reading LAST_ID on OST failed, and it should only deactivate OST in this case.



 Comments   
Comment by Gerrit Updater [ 20/Oct/21 ]

"Lai Siyao <lai.siyao@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/45309
Subject: LU-15133 osp: deactivate OSP on last_id error
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 4105e6acb7580a90854f6965a2ce5b9d922705f7

Comment by Gerrit Updater [ 06/Jan/22 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45309/
Subject: LU-15133 osp: only deactivate OSP on LAST_FID error
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: f738156aa621c6c800d08af18ca52c39c40c3bd3

Comment by Peter Jones [ 06/Jan/22 ]

Landed for 2.15

Generated at Sat Feb 10 03:15:44 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.