public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Frederic Giasson <fgiasson@mediatrix.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: Endless gc spining on nearly full JFFS2 fs
Date: Tue, 30 Apr 2002 13:43:02 +0100	[thread overview]
Message-ID: <20574.1020170582@redhat.com> (raw)
In-Reply-To: <F1BED55F35F4D3118C0F00E0295CFF4D014ECEDE@mail.mediatrix.com>

fgiasson@mediatrix.com said:
>     I have noticed that the gc sometimes seems to spin-around for a
> very long time, if not endlessly, when files are copied to a nearly
> full JFFS2 drive.  

Hmmm. This shouldn't happen. Can you provide a log with the debugging 
enabled? Somehow, some space is being marked dirty when we're 
garbage-collecting, so it thinks it can still make some progress.

--
dwmw2

      reply	other threads:[~2002-04-30 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30 12:40 Endless gc spining on nearly full JFFS2 fs Frederic Giasson
2002-04-30 12:43 ` David Woodhouse [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=20574.1020170582@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=fgiasson@mediatrix.com \
    --cc=linux-mtd@lists.infradead.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