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 q3GNv1M8257235 for ; Mon, 16 Apr 2012 18:57:01 -0500 Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by cuda.sgi.com with ESMTP id dK71THecdooEMfgy for ; Mon, 16 Apr 2012 16:56:59 -0700 (PDT) Date: Tue, 17 Apr 2012 09:56:47 +1000 From: Dave Chinner Subject: Re: XFS blocked task in xlog_cil_force_lsn Message-ID: <20120416235647.GA6734@dastard> References: <4F8BC0B9.90604@profihost.ag> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4F8BC0B9.90604@profihost.ag> 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: Stefan Priebe - Profihost AG Cc: Christoph Hellwig , Greg KH , Philipp Herz - Profihost AG , stable@vger.kernel.org, "xfs@oss.sgi.com" On Mon, Apr 16, 2012 at 08:48:25AM +0200, Stefan Priebe - Profihost AG wrote: > Hi, > > today i've seen this call trace / block in XFS while running 3.0.27. > > INFO: task xfsaild/sdc3:1818 blocked for more than 120 seconds. > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > xfsaild/sdc3 D ffff88041f374dc8 0 1818 2 0x00000000 > ffff88041edd3d30 0000000000000046 ffff8803ecaa8dc0 ffff88041f23fe28 > ffff88041f374860 0000000000010800 ffff88041edd3fd8 ffff88041edd2010 > ffff88041edd3fd8 0000000000010800 ffff88041f15c860 ffff88041f374860 > Call Trace: > [] schedule+0x3a/0x60 > [] xlog_cil_force_lsn+0xe9/0x110 > [] ? try_to_wake_up+0x2a0/0x2a0 > [] _xfs_log_force+0x62/0x250 > [] xfs_log_force+0x13/0x40 > [] ? xfs_trans_ail_cursor_next+0x27/0x30 > [] xfsaild+0x447/0x460 > [] ? xfs_trans_ail_init+0xb0/0xb0 > [] kthread+0x96/0xa0 > [] kernel_thread_helper+0x4/0x10 > [] ? kthread_worker_fn+0x130/0x130 > [] ? gs_change+0xb/0xb > > Is there a known fix / patch available? Your first question should be: is this a known problem? And the answer to that is: I don't think so. So, is the system actually hung? Were there IO errors around this time? did the system recover and continue to work normally? What's your storage hardware, application, workload, etc? Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs