看板 Dfbsd_Bugs
作者
留言 0則留言,0人參與討論
推噓 0  ( 0推 0噓 0→ )
Issue #2249 has been updated by Antonio M. Huete Jimenez. Rumko, It's indeed a deadlock. I'm experiencing that during 'hammer cleanup' also but on x86_64. Explanation from Matt: 21:21 <@dillon> the pageout daemon deadlock is because the hammer backend locks hammer inodes and the pageout daemon frontend can only detect locked vnodes 21:21 <@dillon> so the pageout daemon will happily lock a vnode and then issue the pageout request to the hammer backend and cause the hammer backend to get stuck on the inode (waiting for new memory) It doesn't seem to have an easy solution. Cheers, Antonio Huete ---------------------------------------- Bug #2249: deadlock under high i/o load (e.g. hammer reblock) http://bugs.dragonflybsd.org/issues/2249 Author: Rumko Rumko Status: New Priority: Normal Assignee: Category: Target version: Almost latest master (last commit from upstream should be 0e84c0db0d0bcd6d681bc30fd16e96c26bb92db2). Whenever nightly cron runs and a few minutes after hammer cleanup starts doing it's job, the machine becomes mostly unresponsive (most processes and most ssh connections stop responding, but strangely pf still continues doing it's job). Fortunately debugging through serial console still worked, so the dump is available at leaf:~rumko/crash/deadlock/*.0 . -- Please do not CC me, since I already receive everything from these MLs. Regards, Rumko -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account