From: David Chinner <dgc@sgi.com>
To: Damien Wyart <damien.wyart@free.fr>
Cc: David Chinner <dgc@sgi.com>,
Christoph Hellwig <hch@infradead.org>,
Lachlan McIlroy <lachlan@sgi.com>, Peter Leckie <pleckie@sgi.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-xfs@oss.sgi.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Important regression with XFS update for 2.6.24-rc6
Date: Tue, 18 Dec 2007 23:24:45 +1100 [thread overview]
Message-ID: <20071218122445.GJ4396912@sgi.com> (raw)
In-Reply-To: <20071218112804.GA3069@localhost.localdomain>
On Tue, Dec 18, 2007 at 12:28:04PM +0100, Damien Wyart wrote:
> Hello,
>
> As a follow-up to <http://marc.info/?l=linux-kernel&m=119796120524618&w=2>
> (LKML seems down right now so I am not linking to it), I have detected an
> important problem with these two patches: after applying them by hand
> (downloaded them raw from SGI's gitweb) on top of 2.6.24-rc5-git5 (they have
> not yet been pulled into mainline by Linux as of this morning) for testing
> purposes, I noticed upon reboot that "ls -l" on directories with many files
> and subdirectories (around 5000 entries) takes several hundreds of MB in RAM
> and then dies with "memory exhausted" error.
Ok. I haven't noticed anything wrong with directories up to about 250,000
files in the last few days. The ls -l I just did on a directory with
15000 entries (btree format) used about 5MB of RAM. extent format
directories appear to work fine as well (tested 500 entries).
Can you:
a) isolate the problem to one patch or the other. My guess
would be the directory mod, but.....
b) show your working ;)
- what platform (i386, x86_64, etc)
- what debug options
- commands and output that shows the problem
- strace of ls -l going bad
- xfs_info from filesystem in question
> I also noticed that ldconfig takes a lot of time to complete, and firefox
> seems also to eat much more memory than usual. Reverting the two patches
> (going back to vanilla rc5-git5) makes these problems go away. I am not
> able to test right now if only one of the patches is bogus or if both of
> them are concerned.
Well, there goes a).....
> As the symptoms are easy to reproduce, I guess this is some kind of brown
> paper bag bug and will be easy for XFS experts to spot.
Well, not reproducable on my test boxes. It may well be a brown paper
bag job, but it's not obvious.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-12-18 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 11:28 Important regression with XFS update for 2.6.24-rc6 Damien Wyart
2007-12-18 12:24 ` David Chinner [this message]
2007-12-18 14:30 ` Damien Wyart
2007-12-18 15:19 ` David Chinner
2007-12-19 10:45 ` David Chinner
2007-12-19 11:17 ` Damien Wyart
2007-12-19 11:31 ` David Chinner
2007-12-20 1:56 ` [review please] " David Chinner
2007-12-20 5:01 ` Timothy Shimmin
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=20071218122445.GJ4396912@sgi.com \
--to=dgc@sgi.com \
--cc=damien.wyart@free.fr \
--cc=hch@infradead.org \
--cc=lachlan@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=pleckie@sgi.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.