[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1303990590.2081.9.camel@lenovo>
Date: Thu, 28 Apr 2011 12:36:30 +0100
From: Colin Ian King <colin.king.lkml@...il.com>
To: James Bottomley <James.Bottomley@...e.de>
Cc: Chris Mason <chris.mason@...cle.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: [BUG] fatal hang untarring 90GB file, possibly writeback
related.
One more data point to add, I've been looking at an identical issue when
copying large amounts of data. I bisected this - and the lockups occur
with commit
3e7d344970673c5334cf7b5bb27c8c0942b06126 - before that I don't see the
issue. With this commit, my file copy test locks up after ~8-10
iterations, before this commit I can copy > 100 times and don't see the
lockup.
On Wed, 2011-04-27 at 15:05 -0500, James Bottomley wrote:
> 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 from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists