From: Andrew Morton <akpm@digeo.com>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org, sct@redhat.com, adilger@clusterfs.com
Subject: Re: 2.5.66: slow to friggin slow journal recover
Date: Fri, 11 Apr 2003 19:24:13 -0700 [thread overview]
Message-ID: <20030411192413.279f0574.akpm@digeo.com> (raw)
In-Reply-To: <20030412021638.GA650@zip.com.au>
CaT <cat@zip.com.au> wrote:
>
> On Tue, Apr 01, 2003 at 02:28:44AM -0800, Andrew Morton wrote:
> > If the journal recovery is still slow then try capturing the state when it is
> > stuck with sysrq-T.
>
> It finally didn't kill it. This is what it's like when it's not doing
> anything (ie no disk access).
> ...
> fsck.ext3 R CF971E28 4293902656 40 37 (NOTLB)
> Call Trace:
> [<c0118a2e>] io_schedule+0xe/0x18
> [<c012cde8>] wait_on_page_bit+0x9c/0xb8
> [<c0119088>] autoremove_wake_function+0x0/0x3c
> [<c0119088>] autoremove_wake_function+0x0/0x3c
> [<c012d3a2>] do_generic_mapping_read+0x1be/0x328
> [<c012d7a0>] __generic_file_aio_read+0x184/0x1a0
> [<c012d50c>] file_read_actor+0x0/0x110
> [<c012d887>] generic_file_read+0x7f/0x9c
> [<c0138618>] handle_mm_fault+0x68/0xfc
> [<c0116960>] do_page_fault+0x0/0x3fe
> [<c01494ee>] blkdev_file_write+0x26/0x30
> [<c0142f4e>] vfs_read+0xa2/0xd4
> [<c014312a>] sys_read+0x2a/0x40
> [<c0108cf3>] syscall_call+0x7/0xb
OK, you may be thrashing the VM. fsck can use a lot of memory.
How large is the filesystem?
How many files are on the filesystem?
How much physical memory does the machine have?
Run ALT-sysrq-M during the fsck to get some stats.
next prev parent reply other threads:[~2003-04-12 2:12 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
2003-04-11 17:26 ` CaT
2003-04-12 2:16 ` CaT
2003-04-12 2:24 ` Andrew Morton [this message]
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=20030411192413.279f0574.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=adilger@clusterfs.com \
--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®