From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs leaking?
Date: Fri, 11 Jul 2008 21:02:38 -0500 [thread overview]
Message-ID: <487810BE.5050701@sandeen.net> (raw)
In-Reply-To: <4877FC4F.7020906@sandeen.net>
Eric Sandeen wrote:
> 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.
2.6.26-rc9 passed without incident.
> The complete lack of memory may well explain the horrendous repair
> performance, too. :)
about 12min, not bad.
(twice that of e2fsck/ext4 though, for this test!) :)
-Eric
> -Eric
>
>> Cheers,
>>
>> Dave.
>
>
next prev parent reply other threads:[~2008-07-12 2:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 17:04 xfs leaking? Eric Sandeen
2008-07-11 23:38 ` Dave Chinner
2008-07-12 0:35 ` Eric Sandeen
2008-07-12 2:02 ` Eric Sandeen [this message]
2008-07-14 4:07 ` Mark Goodwin
2008-07-14 4:13 ` Christoph Hellwig
2008-07-14 4:15 ` Eric Sandeen
2008-07-12 1:31 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=487810BE.5050701@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox