public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, sct@redhat.com, adilger@clusterfs.com
Subject: Re: 2.5.66: slow to friggin slow journal recover
Date: Sat, 12 Apr 2003 15:13:40 +1000	[thread overview]
Message-ID: <20030412051340.GB455@zip.com.au> (raw)
In-Reply-To: <20030411220158.28f88097.akpm@digeo.com>

On Fri, Apr 11, 2003 at 10:01:58PM -0700, Andrew Morton wrote:
> CaT <cat@zip.com.au> wrote:
> >
> > Do you still want the alt-sysrq-m stuff? And is there anything else I
> > can do? profiling? apply a patch with debugging stuff that'd give you a
> > clue? etc...
> 
> Can't think of a lot really.

doh.

> Are you sure that fsck is only running journal recovery?  Is it possible that
> it is performing a full fsck for some reason?

It's still in the journal stage. 2 reasons lead me to believe this:

1. if I hit ^c then mount does the journal recovery (and does it
   quick-smart - the hd light is on full-force during this)
2. the progress bar that comes up during a full fsck is not displayed.

> Make sure you're running current e2fsprogs?

I've compiled 1.32+1.33-WIP-2003.03.30 (debian e2fsprogs from sid). I'll
install that now.

> Boot with `init=/bin/sh', run fsck by hand in the background, poke around
> with `ps' to see what it's up to, etc.

I'll try to remember to do this when my laptop loses power again (it
happens often - power connector is wonky). Don't wanna do it right now
cos I have the connector in just the right spot so that the laptop is
actually getting power.

-- 
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
	- http://www.informationclearinghouse.info/article2479.htm

      reply	other threads:[~2003-04-12  5:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 10:02 2.5.66: slow to friggin slow journal recover CaT
2003-04-01 10:28 ` 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 [this message]

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=20030412051340.GB455@zip.com.au \
    --to=cat@zip.com.au \
    --cc=adilger@clusterfs.com \
    --cc=akpm@digeo.com \
    --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