[LU-7053] Do not use osd_object_find in osd_index_ea_insert

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.8.0
• Affects Version/s: Lustre 2.8.0
• Severity: 3
• Assignee: Di Wang
• Reporter: Di Wang

Description

Do not use osd_object_find in osd_index_ea_insert() to avoid that notorious object find hung.

Issue Links

• is related to: LU-9972 Performance regressions on unique directory removal

Comments

[Peter Jones]

Landed for 2.8

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/17092/
Subject: LU-7053 osd: don't lookup object at insert
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 9ae3a2891f10a19acf855a90337316dda704da5d

[Gerrit Updater]

Alex Zhuravlev ([e-mail]) uploaded a new patch: http://review.whamcloud.com/17092
Subject: LU-7053 osd: don't lookup object at insert
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 34572a3239fc4a815f520b6849709a2bb31ca677

[Alex Zhuravlev]

well, still the question: who is destroying the object being referenced by a new direntry ?

[Di Wang]

Hmm, this is different issue, do I miss sth?

[Alex Zhuravlev]

would http://review.whamcloud.com/#/c/15924/ help ?

[Di Wang]

I found this problem during racer + migration, and it might cause deadlock if we use os_object_find in osd_index_ea_insert(), because of double object find in one service handler().