| To: | Lachlan McIlroy <lachlan@xxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: another problem with latest code drops |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Sun, 19 Oct 2008 05:10:21 -0400 |
| In-reply-to: | <20081016072019.GH25906@disturbed> |
| References: | <48F6A19D.9080900@sgi.com> <20081016060247.GF25906@disturbed> <48F6EF7F.4070008@sgi.com> <20081016072019.GH25906@disturbed> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Thu, Oct 16, 2008 at 06:20:19PM +1100, Dave Chinner wrote:
> I just ran up the same load in a UML session. I'd say it's this
> slab:
>
> 2482 2481 99% 0.23K 146 17 584K xfs_btree_cur
>
> which is showing a leak. It is slowly growing on my system
> and dropping the caches doesn't reduce it's size. At least it's
> a place to start looking - somewhere in the new btree code we
> seem to be leaking a btree cursor....
I've been running
for i in $(seq 1 8); do
fsstress -p 64 -n 10000000 -d /mnt/data/fsstress.$i &
done
for about 20 hours now, and I'm only up to a few hundred xfs_btree_cur
entires, not changing much at all over time. This is xfs-2.6 on a 4-way
PPC machine.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS filesystem corruption on the arm(el) architecture, Christoph Hellwig |
|---|---|
| Next by Date: | Re: kernel 2.6.27.2 (32bit) filesystem is read-only, Justin Piszcz |
| Previous by Thread: | Re: [PATCH] Re: another problem with latest code drops, Lachlan McIlroy |
| Next by Thread: | Update Your Profile, restoration |
| Indexes: | [Date] [Thread] [Top] [All Lists] |