From: David Woodhouse <dwmw2@infradead.org>
To: rick@efn.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: infinite loop in jffs2_flush_wbuf_gc()?
Date: Thu, 14 Jul 2005 15:39:06 +0100 [thread overview]
Message-ID: <1121351946.16070.32.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <E1Dt4R6-0005UI-00@amazonia.client.comcast.net>
On Thu, 2005-07-14 at 07:11 -0700, Rick Bronson wrote:
> A few seconds after the command line prompt appears the gc code goes
> into a 12 minute temporary "hang" loop in jffs2_flush_wbuf_gc() in
> wbuf.c starting at:
OK. So it _is_ making progress, but just very slowly. It _is_ garbage
collecting, but it's not having to write out new nodes, because it's
mostly just erasing.
Can you build with CONFIG_JFFS2_FS_DEBUG=1 and show the output while
it's doing this? It shouldn't be taking that long -- I wonder what else
is going on.
--
dwmw2
next prev parent reply other threads:[~2005-07-14 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 16:26 infinite loop in jffs2_flush_wbuf_gc()? Rick Bronson
2005-07-08 16:32 ` Artem B. Bityuckiy
2005-07-08 16:59 ` Rick Bronson
2005-07-11 14:55 ` David Woodhouse
[not found] ` <E1Ds2ma-0005ta-00@amazonia.client.comcast.net>
[not found] ` <1121108481.27264.129.camel@hades.cambridge.redhat.com>
[not found] ` <E1Ds4AF-00063d-00@amazonia.client.comcast.net>
[not found] ` <1121115438.3430.6.camel@localhost.localdomain>
[not found] ` <E1DsMIp-0004U9-00@amazonia.client.comcast.net>
[not found] ` <1121181101.12169.4.camel@hades.cambridge.redhat.com>
[not found] ` <E1DsNHk-0004bq-00@amazonia.client.comcast.net>
[not found] ` <1121186381.12086.6.camel@localhost.localdomain>
[not found] ` <E1DsOD0-0004iT-00@amazonia.client.comcast.net>
[not found] ` <1121189272.12224.10.camel@localhost.localdomain>
[not found] ` <E1Dspqm-0003zl-00@amazonia.client.comcast.net>
[not found] ` <1121294622.12224.87.camel@localhost.localdomain>
2005-07-14 14:11 ` Rick Bronson
2005-07-14 14:39 ` David Woodhouse [this message]
2005-07-14 17:14 ` Artem B. Bityuckiy
2005-07-14 17:18 ` Artem B. Bityuckiy
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=1121351946.16070.32.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rick@efn.org \
/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