From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [Bug 18632] "INFO: task" dpkg "blocked for more than 120 seconds. Date: Thu, 9 Jun 2011 04:27:18 -0400 Message-ID: <20110609082718.GA10335@infradead.org> References: <201106082138.p58Lchgj002615@demeter2.kernel.org> <20110608150241.8412a63d.akpm@linux-foundation.org> <20110609033217.GA10741@localhost> <20110609035426.GA12061@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dave Chinner , Christoph Hellwig , Andrew Morton , Jan Kara , linux-fsdevel@vger.kernel.org, "bugzilla-daemon@bugzilla.kernel.org" , daaugusto@gmail.com, kernel-bugzilla@cygnusx-1.org, listposter@gmail.com, justincase@yopmail.com, clopez@igalia.com To: Wu Fengguang Return-path: Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:58910 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752827Ab1FII13 (ORCPT ); Thu, 9 Jun 2011 04:27:29 -0400 Content-Disposition: inline In-Reply-To: <20110609035426.GA12061@localhost> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Jun 09, 2011 at 11:54:26AM +0800, Wu Fengguang wrote: > Oh it's not sync(1) in Carlos' case, but random commands like man/dd > as well as > > task xfssyncd:451 blocked for more than 120 seconds. > > It looks more like XFS related livelock, because I ran into similar > problem in a very simple XFS setup on some plain disk partition. Care to explain what issues you saw, and with what setup and kernel version? Also usually the task blocked more than 120 seconds display should come with a stacktrace, how does it look like?