From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id B6A247F3F for ; Thu, 10 Dec 2015 16:35:59 -0600 (CST) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay3.corp.sgi.com (Postfix) with ESMTP id 47BA6AC002 for ; Thu, 10 Dec 2015 14:35:56 -0800 (PST) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by cuda.sgi.com with ESMTP id Dpp03svXuES0a8px for ; Thu, 10 Dec 2015 14:35:53 -0800 (PST) Date: Fri, 11 Dec 2015 09:35:51 +1100 From: Dave Chinner Subject: Re: handling device or resource busy errors. Message-ID: <20151210223551.GI26718@dastard> References: <20151210021343.GI19802@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="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Ed Peschko Cc: xfs@oss.sgi.com On Wed, Dec 09, 2015 at 11:58:41PM -0800, Ed Peschko wrote: > Dave, > > futex comes from doing a simple strace, which showed the futex as the call > that was being blocked. My fear is that it is a holdover from an old, dead > process; we went through each process on the system and lsof -p'd it, > didn't see anything. Please show your working. i.e. attach the output of strace for whatever process is tripping over this. I've still got no idea what you are talking about, and I won't until I see the output of the commands you are taling about. Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs