[LU-15333] lfsck reports "XATTR trusted.fid: the parent FID is invalid" Created: 07/Dec/21  Updated: 28/Jul/22  Resolved: 07/Jul/22

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

Type: Bug Priority: Major
Reporter: Prasannakumar Nagasubramani Assignee: Alexander Zarochentsev
Resolution: Duplicate Votes: 0
Labels: None
Environment:

client cluster: Walleye-P5
20 x Lustre 2.15 clients
4 X LNet routers
Lustre client: 2.14.55_81_gc26b347
storage cluster: kjcf05
NEO build: 6.0-65-cm-21.10.24-g2c588a6
Lustre server: 2.14.55_81_gc26b347
Model SSUs: 1xE1000D 1xE1000F
4 x OSS nodes with 2 x HDD OSTs and 2 x flash OSTs

Issue Links:
Duplicate
duplicates LU-15683 sanity-flr.sh test_50c: proper initia... Resolved
Related
is related to LU-15404 kernel panic and filesystem corruptio... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

LFSCK test reports "XATTR trusted.fid: the parent FID is invalid" error in the current 2.15 run.

00100000:10000000:4.0:1637044175.473115:0:148585:0:(lfsck_namespace.c:264:lfsck_namespace_record_failure()) kjcf05-MDT0000-osd: namespace LFSCK hit first non-repaired inconsistency at the pos [2633473, [0x0:0x0:0x0], 0x0]
00100000:10000000:26.0:1637044377.319767:0:148587:0:(lfsck_layout.c:4153:lfsck_layout_check_parent()) kjcf05-MDT0000-osd:([0x20000ea75:0xee9:0x0]|[0x0:0x0:0x0])/[0x100010000:0x6fb6352:0x0]:XATTR trusted.fid: the parent FID is invalid

Will upload lfsck logs to the FTP.

 

 Comments   
Comment by Prasannakumar Nagasubramani [ 07/Dec/21 ]

LFSCK logs uploaded to FTP.

ftp> put lfsck_gc26b347.tar.gz
local: lfsck_gc26b347.tar.gz remote: lfsck_gc26b347.tar.gz
227 Entering Passive Mode (50,222,100,36,211,43).
150 Ok to send data.
226 Transfer complete.
1875396 bytes sent in 0.0423 secs (44349.23 Kbytes/sec)
ftp> pwd
257 "/uploads/LU15333"
ftp>
Comment by Peter Jones [ 19/Jan/22 ]

Cory

Is someone from your team investigating this reported issue?

Peter

Comment by Cory Spitz [ 20/Jan/22 ]

Yes, Zam is investigating this issue. I believe it is fallout from LU-15404 where LFSCK is finding the non-Lustre EA inodes, which lack FID linkage. Since LFSCK does the right thing and reports the issue (while leaving it up to e2fsck to solve), I think we should resolve it as not a bug. Zam, do you agree? Please correct me if I'm wrong.

Comment by Sergey Cheremencev [ 07/Jul/22 ]

Looks like a dup of https://jira.whamcloud.com/browse/LU-15683. Propose to close this one.

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