From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Fri, 11 Jul 2008 17:34:26 -0700 (PDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m6C0YMkK001008 for ; Fri, 11 Jul 2008 17:34:23 -0700 Received: from sandeen.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 47FB92E048D for ; Fri, 11 Jul 2008 17:35:28 -0700 (PDT) Received: from sandeen.net (sandeen.net [209.173.210.139]) by cuda.sgi.com with ESMTP id KIhUIK8iomlbfLbx for ; Fri, 11 Jul 2008 17:35:28 -0700 (PDT) Message-ID: <4877FC4F.7020906@sandeen.net> Date: Fri, 11 Jul 2008 19:35:27 -0500 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: xfs leaking? References: <4877928A.1020008@sandeen.net> <20080711233832.GH11558@disturbed> In-Reply-To: <20080711233832.GH11558@disturbed> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: Eric Sandeen , xfs-oss Dave Chinner wrote: > I'd suggest updating to 2.6.26-rc9 and repeating the test. After > unmounting all the filesystems and before you rmmod the kernel > module, dump /proc/slabinfo so we can see if there are remaining > objects in the XFs slabs.... Yep I fired up on 2.6.26-rc9 this morning after I sent the mail. And I wish I'd checked the slabs before the explosion last time ... it'll be full again in a while and I'll try again. The complete lack of memory may well explain the horrendous repair performance, too. :) -Eric > Cheers, > > Dave.