public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Cc: sct@redhat.com, akpm@zip.com.au, adilger@clusterfs.com
Subject: 2.5.66: slow to friggin slow journal recover
Date: Tue, 1 Apr 2003 20:02:37 +1000	[thread overview]
Message-ID: <20030401100237.GA459@zip.com.au> (raw)

The journal recovery rangers from slow to really friggin slow under
2.5.66 with definate pauses in disk io stretching for 10s of seconds.
This does not happen with 2.5.63 and if I hit ^c on fsck and let the
kernel handle the journal recover for all partitions  on mountime
the recovery under 2.5.66 is either so fast that you don't notice
it or just a buttload faster. Very objective measurements of time but
the slowness of a journal recover as done by fsck is so noticible it's
not funny.

At the time of fsck journal recover or moiunt-time kernel journal
recover DMA is turned on the drive.

e2fsprogs 1.27 is in use. (1.27-2 from debian woody)

-- 
"Other countries of course, bear the same risk. But there's no doubt his
hatred is mainly directed at us. After all this is the guy who tried to
kill my dad."
        - George W. Bush Jr, Leader of the United States Regime
          September 26, 2002 (from a political fundraiser in Houston, Texas)

             reply	other threads:[~2003-04-01  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 10:02 CaT [this message]
2003-04-01 10:28 ` 2.5.66: slow to friggin slow journal recover Andrew Morton
2003-04-11 17:26   ` CaT
2003-04-12  2:16   ` CaT
2003-04-12  2:24     ` Andrew Morton
2003-04-12  2:38       ` CaT
2003-04-12  2:53         ` Andrew Morton
2003-04-12  4:48           ` CaT
2003-04-12  5:01             ` Andrew Morton
2003-04-12  5:13               ` CaT

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=20030401100237.GA459@zip.com.au \
    --to=cat@zip.com.au \
    --cc=adilger@clusterfs.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox