From: Wolly <wwolly@gmx.net>
To: Chris Mason <mason@suse.com>, linux-kernel@vger.kernel.org
Subject: Re: Huge disk performance degradation STILL IN 2.4.10
Date: Mon, 24 Sep 2001 17:05:13 +0200 [thread overview]
Message-ID: <200109241505.RAA12224@enigma.deepspace.net> (raw)
In-Reply-To: <200109211723.TAA00638@enigma.deepspace.net> <200109232319.BAA02449@enigma.deepspace.net> <2100580000.1001289300@tiny>
In-Reply-To: <2100580000.1001289300@tiny>
On Monday 24 September 2001 01:55, Chris Mason wrote:
> On Monday, September 24, 2001 01:19:18 AM +0200 Wolly <wwolly@gmx.net>
> wrote:
> > Hi kernel hackers,
> >
> > As soon as 2.4.10 was out, I got the patch and tested it again.
> > The problem is still there and did not get better at all.
>
> Could you please mount the FS with -o notail and try again? I think your
> test is hitting a worst case in the 2.4.x reiserfs tail code.
>
Okay, I plugged some old hd into my computer and formatted one half with
ext2, the other half with reiserfs.
It seems to be definitely a reiserfs issue because I cannot trigger the
performance loss (permament hd head positioning) with ext2. However,
passing -o notail when mounting does not help. (-o notail is accepted and
`bash# mount' displays `/dev/hdxy on /mnt type reiserfs (rw,notail)')
Could you reproduce this? Did you even try?
And why does this not show up on kernels <=2.4.6 and shows up
with linux>=2.4.9 (2.4.7, 2.4.8: unknown)?
-Wolly
next prev parent reply other threads:[~2001-09-24 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 17:23 Huge disk performance degradation in 2.4.9 Wolly
2001-09-21 23:29 ` Steve Kieu
2001-09-23 23:19 ` Huge disk performance degradation STILL IN 2.4.10 Wolly
2001-09-23 23:55 ` Chris Mason
2001-09-24 15:05 ` Wolly [this message]
2001-09-24 15:19 ` Andre Pang
2001-09-25 10:00 ` Wolly
2001-09-30 21:50 ` Tom Vier
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=200109241505.RAA12224@enigma.deepspace.net \
--to=wwolly@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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