From: Andrew Morton <andrewm@uow.edu.au>
To: Mike Black <mblack@csihq.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
"linux-kernel@vger.kernel.or" <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] Re: 2.4.6 and ext3-2.4-0.9.1-246
Date: Sat, 14 Jul 2001 21:58:42 +1000 [thread overview]
Message-ID: <3B5033F2.AF71624E@uow.edu.au> (raw)
In-Reply-To: <02ae01c10925$4b791170$e1de11cc@csihq.com> <3B4BD13F.6CC25B6F@uow.edu.au> <021801c10a03$62434540$e1de11cc@csihq.com> <3B4C729B.6352A443@uow.edu.au> <05c401c10ac1$0e81ad70$e1de11cc@csihq.com> <3B4D8B5D.E9530B60@uow.edu.au> <036e01c10b96$72ce57d0$e1de11cc@csihq.com> <111501c10ba3$664a1370$e1de11cc@csihq.com> <3B4F0273.1DF40F8E@uow.edu.au> <125101c10bc1$85eab630$e1de11cc@csihq.com> <20010713183800.J13419@redhat.com> <001101c10c51$bd6239e0$b6562341@cfl.rr.com>
Mike Black wrote:
>
> Ummm...that would be the version(s) mentioned in the subject line???? :-)
doh.
OK, there was a nasty bug in 0.9.1 which I was not able to trigger
in a solid month's testing. But others with more worthy hardware
were able to find it quite quickly. Stephen fixed it in 0.9.2.
I don't know if it explains the failure you saw. This:
EXT3-fs error (device md(9,0)): ext3_new_inode: reserved
inode or inode > inodes count - block_group = 0,inode=1
is nasty. The LRU cache of inode bitmaps got wrecked. Ugly.
Maybe one more try?
> My .config has
> # CONFIG_NOHIGHMEM is not set
> CONFIG_HIGHMEM4G=y
> # CONFIG_HIGHMEM64G is not set
> CONFIG_HIGHMEM=y
> I've got 2G of RAM
>
> And the main thing I noticed was kswapd going nuts -- this was NOT observed
> with the same tiobench on ext2 (same filesystem). The performance with ext3
> reduced by about 66% on two threads -- and I think that is due to kswapd
> hogging CPU time.
Yup. I've nailed this one - it's lovely.
I'll be back.
-
next prev parent reply other threads:[~2001-07-14 11:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 9:47 2.4.6 and ext3-2.4-0.9.1-246 Mike Black
2001-07-10 17:52 ` Andreas Dilger
[not found] ` <018101c1096a$17e2afc0$b6562341@cfl.rr.com>
2001-07-10 18:17 ` [Ext2-devel] " Stephen C. Tweedie
2001-07-10 18:27 ` Mike Black
2001-07-10 18:29 ` Stephen C. Tweedie
2001-07-10 18:51 ` Andreas Dilger
2001-07-11 4:08 ` Andrew Morton
2001-07-11 12:16 ` Mike Black
2001-07-11 15:36 ` Andrew Morton
2001-07-12 10:54 ` Mike Black
2001-07-12 11:34 ` Andrew Morton
2001-07-13 12:22 ` Mike Black
2001-07-13 13:54 ` Mike Black
2001-07-13 14:15 ` Andrew Morton
2001-07-13 17:30 ` Mike Black
2001-07-13 17:38 ` [Ext2-devel] " Stephen C. Tweedie
2001-07-14 10:42 ` Mike Black
2001-07-14 10:53 ` Andrew Morton
2001-07-14 11:58 ` Andrew Morton [this message]
2001-07-16 18:23 ` Stephen C. Tweedie
2001-07-13 16:30 ` Stephen C. Tweedie
2001-07-13 17:27 ` Steve Lord
2001-07-13 17:33 ` Stephen C. Tweedie
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=3B5033F2.AF71624E@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mblack@csihq.com \
--cc=sct@redhat.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 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.