From mboxrd@z Thu Jan 1 00:00:00 1970 From: Badari Pulavarty Subject: Re: DIO panic on 2.6.21.5 Date: Fri, 29 Jun 2007 17:03:46 -0700 Message-ID: <46859DE2.9040604@us.ibm.com> References: <46832499.40807@us.ibm.com> <5A6608DF-EDC3-43C1-BFB7-58ACBF94DBCB@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel To: Zach Brown Return-path: Received: from e34.co.us.ibm.com ([32.97.110.152]:41792 "EHLO e34.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753702AbXF3ADh (ORCPT ); Fri, 29 Jun 2007 20:03:37 -0400 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e34.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5U03aj2016012 for ; Fri, 29 Jun 2007 20:03:36 -0400 Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l5U03aDk213234 for ; Fri, 29 Jun 2007 18:03:36 -0600 Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l5U03avu016869 for ; Fri, 29 Jun 2007 18:03:36 -0600 Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Zach Brown wrote: > > On Jun 27, 2007, at 8:01 PM, Badari Pulavarty wrote: > >> Hi Zach, >> >> One of our perf. team ran into this while doing some runs. >> I didn't see anything obvious - it looks like we converted >> async IO to synchronous one. I didn't spend much time digging >> around. > > > It looks pretty bad, a *shouldn't happen* kind of case. I'm sure it > just means I missed some case :/. > >> Is this a known issue ? Any ideas ? > > > I haven't seen it before, no. Do they have a reliable recipe to > reproduce it? > > In any case, I'll dig in early next week when I'm back from OLS. I'm > pretty confident that we'll be able to find the case. Please let me > know if it's urgent and I should try and find time before then. > > Thanks for reporting it. I asked our perf. team to reproduce and print out refcount, if this happens again. We can look at it when we get back. Thanks, Badari