From: Andrew Morton <akpm@digeo.com>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org, sct@redhat.com, akpm@zip.com.au,
adilger@clusterfs.com
Subject: Re: 2.5.66: slow to friggin slow journal recover
Date: Tue, 1 Apr 2003 02:28:44 -0800 [thread overview]
Message-ID: <20030401022844.2dee1fe8.akpm@digeo.com> (raw)
In-Reply-To: <20030401100237.GA459@zip.com.au>
CaT <cat@zip.com.au> wrote:
>
> 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)
>
e2fsck 1.32 seems to work fine here.
Try arranging for a partition to _not_ be mounted at boot (disable it in
/etc/fstab). Then do a `reboot -f' and when you get a login prompt, run
e2fsck against that partition.
If the journal recovery is still slow then try capturing the state when it is
stuck with sysrq-T.
next prev parent reply other threads:[~2003-04-01 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 10:02 CaT
2003-04-01 10:28 ` Andrew Morton [this message]
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=20030401022844.2dee1fe8.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--cc=cat@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
all inboxes | Powered by JetHome®