xfs
[Top] [All Lists]

Re: XFS hung on 2.6.33.3 kernel

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: XFS hung on 2.6.33.3 kernel
From: Ilia Mirkin <imirkin@xxxxxxxxxxxx>
Date: Tue, 3 Aug 2010 21:15:53 -0400
Cc: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=8F+EL5dINbXF5Yc2w25k4gW9/KfU0xeelLn3jm5MIkk=; b=OLM8BJcweqSDsiSSjmvB/57WPHkcfhxa/IQczHm4KpqYvCSxHhn5B2Tyo5LMWClZjy UZfVFAUh6PptP7ltvqal+bU+nB4qNgbFMhdub1SK7Fle/ukqqX9vnSPimXiuT63Jr1uu gv2v+iTbGHCsGVq9bEonjQIIilZI1xL8beCYs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=qAm5PFyMtzAba4mvTHPwMCcKgd0KTrGMr/cU6t6e/FUA9GbyZ7FHEO5Uxdcf4zyhvY +R/Qg2pr7Uzoox3l4QHJZYeupP0g3QGqOuXHejva88R2HYFTHww/aU8flf7MlTDwel9K YnbFiDoDapSRoLMvzEzJJL9Udf0ykTlABxnH4=
In-reply-to: <20100804004746.GT7362@dastard>
References: <AANLkTilX3l8TbUztLStj_u9OqOZnBrsNQxmeV4DuBmYJ@xxxxxxxxxxxxxx> <20100718012033.GA18888@dastard> <AANLkTikEv75KRyRTs4awmG894NSKMnBkJNJPYsypMdWf@xxxxxxxxxxxxxx> <20100718235036.GC32635@dastard> <AANLkTi=EzePfBRdEFQo2BRtKy=464Ci6zPG=UyYJiwNp@xxxxxxxxxxxxxx> <20100804004746.GT7362@dastard>
Sender: ibmirkin@xxxxxxxxx
On Tue, Aug 3, 2010 at 8:47 PM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
> Ilia,
>
> Can you send me the output of this for your kernel that the
> traces came from:
>
> $ gdb <path/to/vmlinux>
> (gdb) l *( xfs_write+0x2cc)
>
> You can run it against the vmlinux file in the kernel build
> directory.  Basically 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 = XFS_IOLOCK_EXCL;
595                             need_i_mutex = 1;
596                             mutex_lock(&inode->i_mutex);
597                             xfs_ilock(xip, XFS_ILOCK_EXCL|iolock);
598                             goto start;
599                     }
600             }
601

Well, at least it points at an xfs_ilock, so pretty good chance that
adding debug info didn't change anything else.

<Prev in Thread] Current Thread [Next in Thread>