From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 Description of problem: kjournald is missing a check to JFS_UNMOUNT before it schedules away in it's main function (kjournald() in fs/jbd/journal.c). If a journal is initialized and quickly shut down (as may happen during OCFS2 recovery of a node) the call to journal_destroy() will hang in journal_kill_thread() waiting for kjournald() to see the JFS_UNMOUNT. A very small patch to fix this can be found at: http://marc.theaimsgroup.com/?l=ext2-devel&m=112077008603349&w=2 Version-Release number of selected component (if applicable): How reproducible: Sometimes Steps to Reproduce: 1.call journal_init_inode() 2.call journal_load() 3.call journal_destroy() Additional info:
Created attachment 116531 [details] Patch to fix this
Patch looks OK to me; it has been proposed upstream and I've ACKed it there too.
Sunil.Mushran on oracle-list, confirmed this fix.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-514.html