Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 08 Nov 2005 09:53:00 -0800 (PST) Received: from omx2.sgi.com (omx2-ext.sgi.com [192.48.171.19]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id jA8HqvO0007227 for ; Tue, 8 Nov 2005 09:52:57 -0800 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [198.149.16.15]) by omx2.sgi.com (8.12.11/8.12.9/linux-outbound_gateway-1.1) with ESMTP id jA8Ix0Vv028901 for ; Tue, 8 Nov 2005 10:59:00 -0800 Received: from [128.162.232.50] (stout.americas.sgi.com [128.162.232.50]) by flecktone.americas.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id jA8HmcDN19476593; Tue, 8 Nov 2005 11:48:39 -0600 (CST) Message-ID: <4370E4F6.7060200@sgi.com> Date: Tue, 08 Nov 2005 11:48:38 -0600 From: Eric Sandeen User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Philipp Reisner CC: linux-xfs@oss.sgi.com Subject: Re: XFS unstable with little memory; OOPS in prune_dcache() References: <200511081425.06695.philipp.reisner@linbit.com> <17264.52374.316530.749268@base.ty.sabi.co.UK> <200511081738.31746.philipp.reisner@linbit.com> In-Reply-To: <200511081738.31746.philipp.reisner@linbit.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 6535 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 589 Lines: 15 Philipp Reisner wrote: > Well, yes and no. Although adding RAM solves the problem for me, and > if my attitude was, I need it to work for my, forget the rest. > I would not have posted this message. > > What I see here, that I triggered a problem that the XFS developers > might not be aware of. Maybe they are happy that someone showed them > an unusual corner case and can fix the issue. Maybe they will simply > ignore me. It's always good to have these datapoints & bug reports. On the other hand, nothing in the backtrace immediately suggests that this is an xfs bug... -Eric