https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-17267 Lustre <p>Please advise how to correct a number of files with the same issue:</p> <p>ls -l returns error</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> [root@nbp10-srv1 data]# ls -l  weld_analysis ls: cannot access <span class="code-quote">'weld_analysis'</span>: Numerical result out of range </pre> </div></div> <p>directory is on MDT0001</p> <p>Debug output shows (full debug will be attached)</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> 00000004:00020000:1.0:1699293797.851375:0:2470770:0:(mdt_handler.c:1454:mdt_getattr_internal()) nbp10-MDT0001: getattr error <span class="code-keyword">for</span> [0xdc0003712:0x4e9b:0x0]: rc = -34 </pre> </div></div> <p>stat of fid on the MDT looks like this</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> debugfs:  stat 0xdc0003712:0x4e9b:0x0 Inode: 306186733   Type: directory    Mode:  0700   Flags: 0x80000 Generation: 2816394278    Version: 0x00000000:00000000 User: 11810   Group: 41007   Project:     0   Size: 4096 File ACL: 2379763458 Links: 4   Blockcount: 16 Fragment:  Address: 0    <span class="code-object">Number</span>: 0    Size: 0  ctime: 0x5d759848:00000000 -- Sun Sep  8 17:09:44 2019  atime: 0x6515f065:00000000 -- Thu Sep 28 14:30:13 2023  mtime: 0x5d759848:00000000 -- Sun Sep  8 17:09:44 2019 crtime: 0x5fd3066d:379a1ac8 -- Thu Dec 10 21:41:01 2020 Size of extra inode fields: 32 Extended attributes:   lma: fid=[0xdc0003712:0x4e9b:0x0] compat=0 incompat=c   trusted.lov (352)   trusted.dmv (352)   linkea: idx=0 parent=[0x200000a37:0xb:0x0] name=<span class="code-quote">'weld_analysis'</span> EXTENTS: (0):2379763457 </pre> </div></div> LU-17267

mdt_getattr_internal()) nbp10-MDT0001: getattr error for [0xdc0003712:0x4e9b:0x0]: rc = -34

Bug Critical Open Unresolved Lai Siyao Mahmoud Hanafi Mon, 6 Nov 2023 18:15:50 +0000 Fri, 19 Jan 2024 20:23:03 +0000 Lustre 2.15.3 0 5 <p>I brefely started lfsck in dry-run on MDT0001 got lots of ugliness  right away.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: namespace LFSCK add flags <span class="code-keyword">for</span> [0xdc0002c7a:0x14617:0x0] in the trace file, flags 2, old 0, <span class="code-keyword">new</span> 2: rc = -22 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: namespace LFSCK assistant fail to handle the entry: [0x0:0x0:0x0], parent [0xdc0002c7a:0x14617:0x0], name ..: rc = -22 Nov  6 10:34:37 nbp10-srv3 kernel: CPU: 6 PID: 2704006 Comm: lfsck_namespace Kdump: loaded Tainted: G           OE    --------- -  - 4.18.0-477.10.1.el8_lustre.x86_64 #1 Nov  6 10:34:37 nbp10-srv3 kernel: Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 04/20/2023 Nov  6 10:34:37 nbp10-srv3 kernel: Call Trace: Nov  6 10:34:37 nbp10-srv3 kernel: dump_stack+0x41/0x60 Nov  6 10:34:37 nbp10-srv3 kernel: lfsck_trans_create.part.58+0x63/0x70 [lfsck] Nov  6 10:34:37 nbp10-srv3 kernel: lfsck_namespace_trace_update+0x978/0x980 [lfsck] Nov  6 10:34:37 nbp10-srv3 kernel: lfsck_namespace_assistant_handler_p1+0xa36/0x2060 [lfsck] Nov  6 10:34:37 nbp10-srv3 kernel: ? __switch_to_asm+0x43/0x80 Nov  6 10:34:37 nbp10-srv3 kernel: ? __schedule+0x2d9/0x870 Nov  6 10:34:37 nbp10-srv3 kernel: lfsck_assistant_engine+0x363/0x1c40 [lfsck] Nov  6 10:34:37 nbp10-srv3 kernel: ? __switch_to+0x10c/0x450 Nov  6 10:34:37 nbp10-srv3 kernel: ? finish_task_switch+0x86/0x2e0 Nov  6 10:34:37 nbp10-srv3 kernel: ? __schedule+0x2d9/0x870 Nov  6 10:34:37 nbp10-srv3 kernel: ? finish_wait+0x80/0x80 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8bc:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: ? lfsck_master_engine+0xcd0/0xcd0 [lfsck] Nov  6 10:34:37 nbp10-srv3 kernel: kthread+0x134/0x150 Nov  6 10:34:37 nbp10-srv3 kernel: ? set_kthread_struct+0x50/0x50 Nov  6 10:34:37 nbp10-srv3 kernel: ret_from_fork+0x1f/0x40 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: namespace LFSCK add flags <span class="code-keyword">for</span> [0xdc0002c82:0x1b015:0x0] in the trace file, flags 2, old 0, <span class="code-keyword">new</span> 2: rc = -22 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: namespace LFSCK assistant fail to handle the entry: [0x0:0x0:0x0], parent [0xdc0002c82:0x1b015:0x0], name ..: rc = -22 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8bd:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8be:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8bf:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8c0:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8c1:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8c2:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8c3:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8c4:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8c5:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8c6:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8c7:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8c8:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8c9:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8ca:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8cb:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8cc:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8cd:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8ce:0x0]: rc = 448 Nov  6 10:34:37 nbp10-srv3 kernel: Lustre: nbp10-MDT0001-osd: layout LFSCK master found bad lmm_oi <span class="code-keyword">for</span> [0xdc0002c7e:0x1f8cf:0x0]: rc = 448 </pre> </div></div> <p> </p> <p> </p> <p>Hi Lai</p> <p>Could you please advise here?</p> <p>Thanks</p> <p>Peter</p> <p>Do you have any idea how these files become inaccessible? Can they be accessed before?</p> <p>No idea how they became in this state. I am sure they were ok at some time because the user was using them. There is several directories in this state. </p> <p>I like to get an update on this case.</p> <p>The default LMV of those directories are invalid: the default LMV size should always be '48', but debugfs result shows it's 352, therefore reading default LMV failed with -ERANGE (-34). You may delete the default LMV by debugfs: ea_rm &lt;dirname&gt; trusted.dmv.</p> <p>Mahmoud</p> <p>Have you tried the procedure outlined above?</p> <p>Peter</p> Development Rank 1|i040sf: Rank (Obsolete) 9223372036854775807 Severity