From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id n47NtjQ9237228 for ; Thu, 7 May 2009 18:55:45 -0500 Received: from mail.sandeen.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 7EBA226F79A for ; Thu, 7 May 2009 16:55:48 -0700 (PDT) Received: from mail.sandeen.net (sandeen.net [209.173.210.139]) by cuda.sgi.com with ESMTP id lZC36DLyQ9ex4nil for ; Thu, 07 May 2009 16:55:48 -0700 (PDT) Message-ID: <4A037503.1070904@sandeen.net> Date: Thu, 07 May 2009 18:55:47 -0500 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: 2.6.30-rc4: xfs_fsr hangs References: <4A036FBC.9020201@sandeen.net> In-Reply-To: <4A036FBC.9020201@sandeen.net> 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: Alexander Beregalov Cc: Kernel Testers List , Linux Kernel Mailing List , xfs@oss.sgi.com Eric Sandeen wrote: > there are 2 subsequent unlocks for the same inode: > > 1: > xfs_iunlock: ip ca2304c0 ino 132 flags 0x5 ... > 2: > xfs_iunlock: ip ca230980 ino 131 flags 0x5 Ugh no, those are 2 different inodes.... I can read, really. :) still, looking into it. -Eric _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs