[LU-19855] e2fsck incorrectly links EA inodes to lost+found

• Type: Bug
• Resolution: Unresolved
• Priority: Critical
• Labels: CEA
• Severity: 3
• Assignee: Etienne Aujames
• Reporter: Etienne Aujames

Description

e2fsck complains about "Unattached inodes" after running it on a MDT at the CEA:

Shine.Lustre.Actions.Fsck INFO xxxx-MDT0001 b'Pass 4: Checking reference counts'
Shine.Lustre.Actions.Fsck INFO xxxx-MDT0001 b'Unattached inode 238467314'
Shine.Lustre.Actions.Fsck INFO xxxx-MDT0001 b'Connect to /lost+found? yes'
....

These are EA inodes (ea_inode feature, contained trusted.link data):

debugfs> stat <238467339>
Inode: 238467339   Type: regular    Mode:  0600   Flags: 0x200000     <--- EA_INODE_FL
Generation: 1304211708    Version: 0x00000000:00000001
User: 13639   Group: 32063   Project:     0   Size: 4071
File ACL: 0
Links: 1   Blockcount: 8
Fragment:  Address: 0    Number: 0    Size: 0
 ctime: xxxx -- Thu Jan  1 01:00:00 1970
 atime: xxxx -- Wed Nov  5 11:50:37 2188
 mtime: xxxx -- Thu Jan  1 08:52:51 2026
crtime: xxxx -- Thu Jan  1 08:52:51 2026
Size of extra inode fields: 32
BLOCKS:
(0):149628227
TOTAL: 1

But the EA inodes are connected to parents inodes (found via trusted.link data contained in the EA inode):

Inode: 238467186   Type: regular    Mode:  0644   Flags: 0x0
Generation: 642869650    Version: xxxxx
User: 13639   Group: 32063   Project:     0   Size: 0
File ACL: 0
Links: 104   Blockcount: 8
[...]

inode <238467339> linkea: idx=0 ....
....