From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail191.messagelabs.com (mail191.messagelabs.com [216.82.242.19]) by kanga.kvack.org (Postfix) with ESMTP id AC8966B0011 for ; Wed, 27 Apr 2011 16:05:24 -0400 (EDT) Subject: Re: [BUG] fatal hang untarring 90GB file, possibly writeback related. From: James Bottomley In-Reply-To: <1303926637.2583.17.camel@mulgrave.site> References: <1303920553.2583.7.camel@mulgrave.site> <1303921583-sup-4021@think> <1303923000.2583.8.camel@mulgrave.site> <1303923177-sup-2603@think> <1303924902.2583.13.camel@mulgrave.site> <1303925374-sup-7968@think> <1303926637.2583.17.camel@mulgrave.site> Content-Type: text/plain; charset="UTF-8" Date: Wed, 27 Apr 2011 15:05:16 -0500 Message-ID: <1303934716.2583.22.camel@mulgrave.site> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Chris Mason Cc: linux-fsdevel , linux-mm , linux-kernel , linux-ext4 On Wed, 2011-04-27 at 12:50 -0500, James Bottomley wrote: > To test the theory, Chris asked me to try with data=ordered. > Unfortunately, the deadlock still shows up. This is what I get. As another data point: I'm trying the same kernel with CONFIG_PREEMPT enabled. This time the deadlock doesn't happen. Instead, kswapd0 gets pegged at 99% CPU for much of the untar, but it does eventually complete. James -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org