[LU-11218] osp xattr cache brought by mdd_is_parent needs to be invalidated Created: 06/Aug/18  Updated: 04/Dec/18  Resolved: 04/Dec/18

Status: Closed
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Vladimir Saveliev Assignee: Vladimir Saveliev
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
is related to LU-10406 sanity-lfsck test_31c: (4) Fail to re... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

mdd_is_parent() brings link xattrs of not locked objects into osp cache.
If that cache becomes stale a directory rename includes an outdated link xattr into object xattr table. That makes a directory to have more than one link. That also confuses lfsck.



 Comments   
Comment by Gerrit Updater [ 06/Aug/18 ]

Vladimir Saveliev (c17830@cray.com) uploaded a new patch: https://review.whamcloud.com/32942
Subject: LU-11218 mdd: do not cache atributes on mdd_parent_fid
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 092ac85e6d522c5d797686f3be785c778c2d7cbc

Comment by Alex Zhuravlev [ 06/Aug/18 ]

probably https://review.whamcloud.com/#/c/31194/ can help

 

Comment by Vladimir Saveliev [ 07/Aug/18 ]

probably https://review.whamcloud.com/#/c/31194/ can help

Yes, it helps: the sanity.sh:807 from https://review.whamcloud.com/32942 does not fail with it.

Alex, however, that patch seems to get stuck since march. Do you have plans to move it forward?

Comment by Andreas Dilger [ 07/Aug/18 ]

Alex, Vladimir, do you have a preference of which of these two patches to land?

Is one "more complete" than the other? It seems like Alex's LU-10406 patch will also fix the bug with LFSCK, while the patch here will only fix the one MDD case?

I've rebased Alex's patch to verify that it is still working correctly with master (there can be bad interactions if a very old patch is landed without retesting), so if this is the better one to land then it should be ready in a few hours (barring some intermittent failure).

Comment by Alex Zhuravlev [ 08/Aug/18 ]

I think we should land the old (LU-10406) patch as it improves locking/invalidation schema in general.

 

Comment by Vladimir Saveliev [ 04/Dec/18 ]

https://review.whamcloud.com/31194 at LU-10406 fixes this.

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