From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id o744R9Ao008963 for ; Tue, 3 Aug 2010 23:27:10 -0500 Received: from mail.internode.on.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 1A2EB187D11 for ; Tue, 3 Aug 2010 21:35:29 -0700 (PDT) Received: from mail.internode.on.net (bld-mail16.adl2.internode.on.net [150.101.137.101]) by cuda.sgi.com with ESMTP id e4Z8P4d28pM2jrdA for ; Tue, 03 Aug 2010 21:35:29 -0700 (PDT) Date: Wed, 4 Aug 2010 14:27:25 +1000 From: Dave Chinner Subject: Re: XFS hung on 2.6.33.3 kernel Message-ID: <20100804042725.GX7362@dastard> References: <20100718012033.GA18888@dastard> <20100718235036.GC32635@dastard> <20100804004746.GT7362@dastard> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Ilia Mirkin Cc: xfs@oss.sgi.com On Tue, Aug 03, 2010 at 09:15:53PM -0400, Ilia Mirkin wrote: > On Tue, Aug 3, 2010 at 8:47 PM, Dave Chinner wrote: > > Ilia, > > > > Can you send me the output of this for your kernel that the > > traces came from: > > > > $ gdb > > (gdb) l *( xfs_write+0x2cc) > > > > You can run it against the vmlinux file in the kernel build > > directory. =A0Basically I need to know which xfs_ilock() call in > > xfs_write() one of the mysqld-test processes is stuck on. > = > No problem - BTW, I'm running this on a 2.6.33.3 kernel (same as the > one before, although diff hardware). If you want (and are fine with me > "destroying" the current state), I can upgrade it to a kernel of your > choice and repeat the test overnight. > = > Naturally I didn't have CONFIG_DEBUG_INFO in there... just changed > that to Y and recompiled. I'm not entirely sure that this preserves > all the offsets, but at least the BUG-HUNTING doc makes allusions that > it would. > = > (gdb) l *( xfs_write+0x2cc) > 0xffffffff8124342d is in xfs_write (fs/xfs/linux-2.6/xfs_lrw.c:597). > 592 if (!need_i_mutex && (mapping->nrpages || pos > > xip->i_size)) { > 593 xfs_iunlock(xip, XFS_ILOCK_EXCL|iolock); > 594 iolock =3D XFS_IOLOCK_EXCL; > 595 need_i_mutex =3D 1; > 596 mutex_lock(&inode->i_mutex); > 597 xfs_ilock(xip, XFS_ILOCK_EXCL|iolock); Make sense. Can you run 'l *(xfs_ilock+0x2c)' as well? I just need to confirm which lock it has blocked on. Cheers, Dave. -- = Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs