From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q2UG6YFL140251 for ; Fri, 30 Mar 2012 11:06:34 -0500 Date: Fri, 30 Mar 2012 12:06:31 -0400 From: Christoph Hellwig Subject: Re: bug #917 - deadlock on log recovery Message-ID: <20120330160631.GA19594@infradead.org> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Kirill Malkin Cc: xfs-masters@oss.sgi.com, xfs@oss.sgi.com On Thu, Mar 22, 2012 at 01:34:00PM -0400, Kirill Malkin wrote: > Hi, > > I am wondering if someone had a chance to look at the bug #917. I > filed it a couple of weeks ago, but haven?t seen any action. We are > running into it quite a lot, and the only way out of it is to reboot > the OS and drop the log. Below is another stack trace that is slightly > different from the one I filed, but apparently it is the same bug. > > Please let me know if you need any other input. Can you reproduce this with a recent kernel? 2.6.32 is fairly old and a lot of things have changed in this area. I quickly looked over the trace and nothing obvious springs to mind. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs