[LU-13610] ldiskfs_dx_add_entry large directory Created: 29/May/20  Updated: 12/Aug/20  Resolved: 29/May/20

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

Type: Bug Priority: Minor
Reporter: Paul Edmon Assignee: WC Triage
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

CentOS7


Issue Links:
Related
is related to LU-12892 Large directory feature is not enable... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

We are seeing a lot of warnings in our MDT logs:
May 28 19:24:13 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2628: Large directory feature is not enabled on this filesystem
May 28 19:24:14 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2624: inode 71413065: comm mdt00_084: index 2: reach max htree level
2
May 28 19:24:14 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2628: Large directory feature is not enabled on this filesystem
May 28 19:24:14 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2624: inode 71413066: comm mdt01_069: index 2: reach max htree level
2
May 28 19:24:14 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2628: Large directory feature is not enabled on this filesystem
May 28 19:24:15 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2624: inode 71413065: comm mdt02_115: index 2: reach max htree level
2
May 28 19:24:15 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2628: Large directory feature is not enabled on this filesystem
May 28 19:24:17 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2624: inode 71413066: comm mdt02_036: index 2: reach max htree level
2
May 28 19:24:17 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2628: Large directory feature is not enabled on this filesystem
May 28 19:24:21 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2624: inode 71413066: comm mdt03_119: index 2: reach max htree level
2
May 28 19:24:21 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2628: Large directory feature is not enabled on this filesystem
May 28 19:24:21 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2624: inode 71413061: comm mdt00_075: index 2: reach max htree level
2
May 28 19:24:21 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2628: Large directory feature is not enabled on this filesystem
May 28 19:24:25 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2624: inode 71413060: comm mdt03_106: index 2: reach max htree level
2
May 28 19:24:25 holyscratch01mds01 kernel: LDISKFS-fs warning (device dm-4): ldiskfs_dx_add_entry:2628: Large directory feature is not enabled on this filesystem
 

I'm guessing this is related to a directory having too many files in it.  Is there a way to figure out which directory it is?  Can an inode number be correlated back to a filesystem path?

Paul Edmon



 Comments   
Comment by Paul Edmon (Inactive) [ 29/May/20 ]

Also we are seeing this:

May 28 21:45:41 holyscratch01mds01 kernel: Lustre: 180976:0:(osd_handler.c:501:osd_ldiskfs_add_entry()) scratch1-MDT0000: directory (inode: 71413065, FID: [0x20001ef38:0x5b48
:0x0]) has reached maximum entry limit

Comment by Paul Edmon (Inactive) [ 29/May/20 ]

We found this: https://jira.whamcloud.com/browse/LU-12892, and the lfs fid2path tool.  That solved this issue.  Thanks

Comment by Peter Jones [ 30/May/20 ]

Ah great!

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