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-5535 Lustre <p>I came across an IOR process hanging like this on a Lola client:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Aug 22 03:22:22 lola-22 kernel: IOR D 0000000000000001 0 9127 1 0x00000084 Aug 22 03:22:22 lola-22 kernel: ffff8808227199a8 0000000000000086 ffff880494694d20 ffff8805109dae58 Aug 22 03:22:22 lola-22 kernel: ffff880494694d20 ffff8805ccc58e80 ffffffff8100bb8e ffff8808227199a8 Aug 22 03:22:22 lola-22 kernel: ffff880823655ab8 ffff880822719fd8 000000000000fbc8 ffff880823655ab8 Aug 22 03:22:22 lola-22 kernel: Call Trace: Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffff8100bb8e&gt;] ? apic_timer_interrupt+0xe/0x20 Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffff8105545d&gt;] ? mutex_spin_on_owner+0x8d/0xc0 Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffff8152ac2e&gt;] __mutex_lock_slowpath+0x13e/0x180 Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffff8152aacb&gt;] mutex_lock+0x2b/0x50 Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa0e9a87f&gt;] cl_lock_mutex_get+0x6f/0xd0 [obdclass] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa0e9d297&gt;] cl_lock_enclosure+0x187/0x210 [obdclass] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa0e9d363&gt;] cl_lock_closure_build+0x43/0x150 [obdclass] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa138c8bb&gt;] lov_sublock_lock+0x6b/0x2c0 [lov] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa138d148&gt;] lov_lock_use+0x98/0x330 [lov] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa0e9cb95&gt;] cl_use_try+0x175/0x2e0 [obdclass] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa0e9ce5d&gt;] cl_enqueue_try+0x15d/0x300 [obdclass] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa0e9dd1f&gt;] cl_enqueue_locked+0x6f/0x1f0 [obdclass] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa0e9e97e&gt;] cl_lock_request+0x7e/0x270 [obdclass] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa0ea3934&gt;] cl_io_lock+0x3c4/0x560 [obdclass] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa0ea3b72&gt;] cl_io_loop+0xa2/0x1b0 [obdclass] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa14121c2&gt;] ll_file_io_generic+0x412/0x8f0 [lustre] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa0e93ca9&gt;] ? cl_env_get+0x29/0x350 [obdclass] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa1412ee3&gt;] ll_file_aio_write+0x133/0x2b0 [lustre] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffffa14131b9&gt;] ll_file_write+0x159/0x290 [lustre] Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffff811892e8&gt;] vfs_write+0xb8/0x1a0 Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffff81189cb1&gt;] sys_write+0x51/0x90 Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffff810e212e&gt;] ? __audit_syscall_exit+0x25e/0x290 Aug 22 03:22:22 lola-22 kernel: [&lt;ffffffff8100b072&gt;] system_call_fastpath+0x16/0x1b </pre> </div></div> <p>ior-hung.log contains the complete stack dump.</p> LU-5535

IOR hung during sys_write()

Bug Minor Closed Fixed WC Triage Li Wei Fri, 22 Aug 2014 10:33:55 +0000 Mon, 27 Apr 2015 20:49:10 +0000 Mon, 27 Apr 2015 20:49:10 +0000 0 2 <p>how long had it been in this state?</p> <p>From the backtrace, it looks like that the lock cancelation started write back but it couldn't be finished. Did you notice the state of corresponding OST?</p> <p>IIRC, it was later discovered that a bug happened before this and very likely led to the hang. Closing this ticket as "not a bug".</p> Development Rank 1|hzwucn: Rank (Obsolete) 15410 Severity