[LU-10850] empty indexes don't iterate correctly on ldiskfs Created: 26/Mar/18  Updated: 01/Jul/22  Resolved: 06/May/18

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

Type: Bug Priority: Minor
Reporter: John Hammond Assignee: John Hammond
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
is related to LU-10699 replace HSM actions llog with an index Resolved
is related to LU-10865 quota reintegration reported version ... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

When iterating through an empty ldiskfs regular index I see a single "ghost" record which is zerod out. Specifically, when given an empty regular ldiskfs index, load() returns 1 which is wrong. ZFS indexes do not show this issue.



 Comments   
Comment by John Hammond [ 04/Apr/18 ]

It's not that they don't iterate correctly. Rather the issue is that when created ldiskfs IAM indexes have a single zeroed-out key and record. This is easy to fix but it needs a small change in fld.

Comment by Gerrit Updater [ 04/Apr/18 ]

John L. Hammond (john.hammond@intel.com) uploaded a new patch: https://review.whamcloud.com/31871
Subject: LU-10850 fld: handle empty ranges in fld_index_init()
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 2d82c369353c170df079c4def2887894b7665c51

Comment by Gerrit Updater [ 04/Apr/18 ]

John L. Hammond (john.hammond@intel.com) uploaded a new patch: https://review.whamcloud.com/31875
Subject: LU-10850 osd: remove phantom entries from IAM indexes
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 2160d3a730dda266efc224962946807b7d28eb10

Comment by Gerrit Updater [ 06/May/18 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/31871/
Subject: LU-10850 fld: handle empty ranges in fld_index_init()
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 9b5337b695be699ce289d5f509436286d4d7185c

Comment by Peter Jones [ 06/May/18 ]

Landed for 2.12

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