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-1020 Lustre <p>Lustre: DEBUG MARKER: ----<del>============= acceptance-small: racer ============</del>---- Fri Jan 20 18:54:29 PST 2012<br/> general protection fault: 0000 <span class="error">&#91;1&#93;</span> SMP <br/> last sysfs file: /devices/pci0000:00/0000:00:00.0/irq<br/> CPU 3 <br/> Modules linked in: nfs nfs_acl mgc(U) lustre(U) lov(U) mdc(U) lquota(U) osc(U) ksocklnd(U) ko2iblnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U) autofs4 hidp rfcomm l2cap bluetooth lockd sunrpc cpufreq_ondemand acpi_cpufreq freq_table mperf be2iscsi iscsi_tcp bnx2i cnic uio cxgb3i libcxgbi iw_cxgb3 cxgb3 libiscsi_tcp ib_iser libiscsi2 scsi_transport_iscsi2 scsi_transport_iscsi ib_srp rds ib_sdp ib_ipoib ipoib_helper ipv6 xfrm_nalgo crypto_api rdma_ucm rdma_cm ib_ucm ib_uverbs ib_umad ib_cm iw_cm ib_addr ib_sa dm_mirror dm_multipath scsi_dh video backlight sbs power_meter hwmon i2c_ec dell_wmi wmi button battery asus_acpi acpi_memhotplug ac parport_pc lp parport mlx4_ib ib_mad ib_core mlx4_en sg igb mlx4_core shpchp joydev i2c_i801 i7core_edac i2c_core tpm_tis tpm edac_mc 8021q tpm_bios pcspkr serio_raw dca dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache ahci libata sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd<br/> Pid: 17088, comm: rm Tainted: G ---- 2.6.18-274.3.1.el5 #1<br/> RIP: 0010:<span class="error">&#91;&lt;ffffffff88924584&gt;&#93;</span> <span class="error">&#91;&lt;ffffffff88924584&gt;&#93;</span> :ptlrpc:lustre_msg_buf+0x4/0x90<br/> RSP: 0000:ffff8102fce0fcc8 EFLAGS: 00010292<br/> RAX: ffff8102f9e29d20 RBX: ffff81033f80d9c0 RCX: 0000000000000001<br/> RDX: 00000000000000a8 RSI: 0000000000000002 RDI: 5a5a5a5a5a5a5a5a<br/> RBP: ffff810321a09dc0 R08: 4f1a28e800000003 R09: 0000000000000177<br/> R10: 0000000000000000 R11: 0000000000000000 R12: ffff8102fe497800<br/> R13: ffff8102fce0fdf8 R14: ffff81032032f400 R15: ffff81032032f4d0<br/> FS: 00002b7833e086e0(0000) GS:ffff81010b7636c0(0000) knlGS:0000000000000000<br/> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b<br/> CR2: 00000000006b32a0 CR3: 000000031cc0a000 CR4: 00000000000006a0<br/> Process rm (pid: 17088, threadinfo ffff8102fce0e000, task ffff810320dc2820)<br/> Stack: ffff810327bec000 ffff81032032f560 0000000200000401 000000000000da06<br/> 0000000200000401 ffffffff88b094d7 ffff81033f80d9c0 ffff81032c7e1a80<br/> ffff810321a09dc0 ffff8102fce0fdf8 0000000000000000 ffffffff88b0c493<br/> Call Trace:<br/> <span class="error">&#91;&lt;ffffffff88b094d7&gt;&#93;</span> :lustre:ll_och_fill+0x67/0x100<br/> <span class="error">&#91;&lt;ffffffff88b0c493&gt;&#93;</span> :lustre:ll_local_open+0xe3/0x190<br/> <span class="error">&#91;&lt;ffffffff887b8378&gt;&#93;</span> :libcfs:cfs_alloc+0x68/0xc0<br/> <span class="error">&#91;&lt;ffffffff88b0dae6&gt;&#93;</span> :lustre:ll_file_open+0x956/0xd10<br/> <span class="error">&#91;&lt;ffffffff88b0d190&gt;&#93;</span> :lustre:ll_file_open+0x0/0xd10<br/> <span class="error">&#91;&lt;ffffffff8001ec04&gt;&#93;</span> __dentry_open+0xd9/0x1dc<br/> <span class="error">&#91;&lt;ffffffff80027729&gt;&#93;</span> do_filp_open+0x2a/0x38<br/> <span class="error">&#91;&lt;ffffffff800eb454&gt;&#93;</span> do_rmdir+0xcd/0xde<br/> <span class="error">&#91;&lt;ffffffff8001a089&gt;&#93;</span> do_sys_open+0x44/0xbe<br/> <span class="error">&#91;&lt;ffffffff8005d28d&gt;&#93;</span> tracesys+0xd5/0xe0</p> <p>Code: 8b 47 08 3d d0 0b d0 0b 74 09 3d d3 0b d0 0b 75 1b eb 0e 83 <br/> RIP <span class="error">&#91;&lt;ffffffff88924584&gt;&#93;</span> :ptlrpc:lustre_msg_buf+0x4/0x90<br/> RSP &lt;ffff8102fce0fcc8&gt;<br/> &lt;0&gt;Kernel panic - not syncing: Fatal exception</p> Client-1.8.7 rhel5-x86_64<br/> Server-lustre-master build #423(2.1.54) rhel6-x86_64 LU-1020

1.8.7 <-->2.1.54 racer OOPS

Bug Major Resolved Won't Fix Hongchao Zhang Sarah Liu Fri, 20 Jan 2012 22:10:48 +0000 Tue, 11 Aug 2015 19:15:20 +0000 Tue, 11 Aug 2015 19:15:20 +0000 Lustre 2.2.0 Lustre 2.1.1 0 4 <p>Hongchao</p> <p>Please can you look into this one</p> <p>Peter</p> <p>the ptlrpc_request stored in lookup_intent-&gt;d.lustre.it_data is freed(the DISP_ENQ_OPEN_REF flag is set in lookup_intent!),<br/> which cause this general protection fault, it's difficult to know where the request is freed by investigating the code line,<br/> will try to create a debug patch to get more debug info.</p> <p>Lustre Clients:<br/> Tag: 1.8.7-wc1<br/> Distro/Arch: RHEL5/x86_64 (kernel version: 2.6.18-274.3.1.el5)<br/> Build: <a href="http://build.whamcloud.com/job/lustre-b1_8/171/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b1_8/171/</a><br/> Network: TCP (1GigE)<br/> ENABLE_QUOTA=yes</p> <p>Lustre Servers:<br/> Tag: v2_1_1_0_RC2<br/> Distro/Arch: RHEL5/x86_64 (kernel version: 2.6.18-274.12.1.el5_lustre.g4554b65)<br/> Build: <a href="http://build.whamcloud.com/job/lustre-b2_1/41/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_1/41/</a><br/> Network: TCP (1GigE)</p> <p>The same issue occurred while running racer test: <a href="https://maloo.whamcloud.com/test_sets/1c5098c0-579b-11e1-99fa-5254004bbbd3" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/1c5098c0-579b-11e1-99fa-5254004bbbd3</a></p> <p>the debug patch is tracked at <a href="http://review.whamcloud.com/#change,2152" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,2152</a></p> <p>Please note that it is important when fixing 1.8/2.x interop bugs that the fix almost always needs to be done on the 2.x server side, since it is not possible to retroactively fix the existing 1.8.x releases.</p> <p>Please find the log in the attached. If you need any other information please just let me know.</p> <p>the attached log is a little confused, and there is a kernel panic at __audit_syscall_exit, then the system<br/> is rebooted and it encountered OOM during loading the modules at boot. it's much more like issues related to<br/> the linux system environment.</p> <p>How does this differ from <a href="https://jira.whamcloud.com/browse/LU-604" title="1.8&lt;-&gt;2.1 interop: RIP: ptlrpc:lustre_msg_buf+0x4/0x90" class="issue-link" data-issue-key="LU-604"><del>LU-604</del></a>? Does the client include the fix of <a href="https://jira.whamcloud.com/browse/LU-604" title="1.8&lt;-&gt;2.1 interop: RIP: ptlrpc:lustre_msg_buf+0x4/0x90" class="issue-link" data-issue-key="LU-604"><del>LU-604</del></a>?<br/> We at NASA got hit by this after we upgraded servers to 2.1.1 last week. The stack<br/> trace of this looks similar to that of <a href="https://jira.whamcloud.com/browse/LU-604" title="1.8&lt;-&gt;2.1 interop: RIP: ptlrpc:lustre_msg_buf+0x4/0x90" class="issue-link" data-issue-key="LU-604"><del>LU-604</del></a>...</p> <p>yes, it does look similar to <a href="https://jira.whamcloud.com/browse/LU-604" title="1.8&lt;-&gt;2.1 interop: RIP: ptlrpc:lustre_msg_buf+0x4/0x90" class="issue-link" data-issue-key="LU-604"><del>LU-604</del></a>, and the patch could not be included as per the comment in <a href="https://jira.whamcloud.com/browse/LU-604" title="1.8&lt;-&gt;2.1 interop: RIP: ptlrpc:lustre_msg_buf+0x4/0x90" class="issue-link" data-issue-key="LU-604"><del>LU-604</del></a> (included in 1.8.8-wc1)</p> Development Rank 1|hzvy9r: Rank (Obsolete) 9736 Severity