From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id o98KWXWd060456 for ; Fri, 8 Oct 2010 15:32:33 -0500 Received: from smtp.sauce.co.nz (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 2657818E20A6 for ; Fri, 8 Oct 2010 13:33:36 -0700 (PDT) Received: from smtp.sauce.co.nz (smtp.sauce.co.nz [210.48.49.72]) by cuda.sgi.com with ESMTP id oddD6OlLVGf0IkLu for ; Fri, 08 Oct 2010 13:33:36 -0700 (PDT) Message-ID: <4CAF801E.9070906@sauce.co.nz> Date: Sat, 09 Oct 2010 09:33:34 +1300 From: Richard Scobie MIME-Version: 1.0 Subject: Re: ENOSPC at 90% with plenty of inodes List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: xfs@oss.sgi.com James Braid wrote: > Any ideas for how can we go about debugging where ENOSPC is coming > from? Hi James, You're not hitting this issue are you? Regards, Richard _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs