Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757516AbYJGVbz (ORCPT ); Tue, 7 Oct 2008 17:31:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753808AbYJGVbq (ORCPT ); Tue, 7 Oct 2008 17:31:46 -0400 Received: from mx2.redhat.com ([66.187.237.31]:51373 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753264AbYJGVbp (ORCPT ); Tue, 7 Oct 2008 17:31:45 -0400 Message-ID: <48EBD448.1010309@redhat.com> Date: Tue, 07 Oct 2008 16:27:36 -0500 From: Eric Sandeen User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) MIME-Version: 1.0 To: Eric Sandeen CC: Jeremy Fitzhardinge , linux-ext4@vger.kernel.org, Linux Kernel Mailing List Subject: Re: ext4 deadlocks References: <48EBB9E9.4030105@goop.org> <48EBC6B9.7000608@sandeen.net> In-Reply-To: <48EBC6B9.7000608@sandeen.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 763 Lines: 22 Eric Sandeen wrote: > Jeremy Fitzhardinge wrote: >> I tried giving ext4 a spin on my rawhide system, and it appears to >> deadlock pretty quickly: lots of processed blocked in either ext4 or jbd2. >> >> From the look of the sysrq-t dumps I captured, I think beagled is >> what's triggering it by doing something with EAs. I haven't had any >> lockups since I killed it off. >> ok I can reproduce this too. I'm guessing this is a migrated ext3 filesystem? I'll sort out a fix soon. Thanks for the report, -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/