Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 22 Jan 2005 14:13:11 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id j0MMD7Df032343 for ; Sat, 22 Jan 2005 14:13:07 -0800 Received: (from xfs@localhost) by oss.sgi.com (8.13.0/8.12.8/Submit) id j0MMD7IU032342 for linux-xfs@oss.sgi.com; Sat, 22 Jan 2005 14:13:07 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id j0MMD6M0032325 for ; Sat, 22 Jan 2005 14:13:06 -0800 Received: (from apache@localhost) by oss.sgi.com (8.13.0/8.12.8/Submit) id j0MLquTq031934; Sat, 22 Jan 2005 13:52:56 -0800 Date: Sat, 22 Jan 2005 13:52:56 -0800 Message-Id: <200501222152.j0MLquTq031934@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 290] XFS Kernel Memory Leak X-Bugzilla-Reason: AssignedTo X-Virus-Scanned: ClamAV 0.80/650/Sun Jan 2 19:00:02 2005 clamav-milter version 0.80j on 127.0.0.1 X-Virus-Scanned: ClamAV 0.80/650/Sun Jan 2 19:00:02 2005 clamav-milter version 0.80j on 127.0.0.1 X-Virus-Status: Clean X-Virus-Status: Clean X-archive-position: 4794 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: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1053 Lines: 31 http://oss.sgi.com/bugzilla/show_bug.cgi?id=290 erek@necrotec.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From erek@necrotec.com 2005-22-01 13:52 PDT ------- well.. this isn't a bug specific to XFS Filesystem... i changed my root partition to ext3 and unmounted all XFS partitions... needless to say.. running updatedb revealed the same problems...memory usage exploding through the roof.. http://bugs.gentoo.org/show_bug.cgi?id=36855 this puts some more insight into the topic.. but.. i ran "emerge sync" (uses rsync).. and the ram used up was _not_ able to be reclaimed... i guess "Resolving this as INVALID" makes sense cause it's not specific to XFS as far as i can see... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.