public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: joakim.tjernlund@lumentis.se
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2_gcd_mtd4 <defunct>
Date: Sun, 23 Sep 2001 16:12:54 +0100	[thread overview]
Message-ID: <6549.1001257974@redhat.com> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLEEDLEPAA.joakim.tjernlund@lumentis.se>

joakim.tjernlund@lumentis.se said:
> When i mount a jffs2 FS as root FS I get this [jffs2_gcd_mtd4 <defunct>
> ] process(and a [jffs2_gcd_mtd4] process as well). This will not
> happen if I mount jffs2 as a extra FS after boot(mount /dev/mtdblock4 /
> jffs2)

Init doesn't reap children which are already dead by the time it's started. 
I think this was declared to be a bug in init itself.


> We are suffering somewhat from long mount times and I remember
> something about checkpoints in jffs2 would solve this problem.
> Correct?

> Anybody working on this? I would be happy to do some testing if
> needed. 

Many people have been talking about it. I've seen no code yet, nor even 
serious debate on the details of how to do it.


> I remember seeing something about beeing alble to control the
> compression level in jffs2(at mount time?), but I can not find in the
> sources. Is it implemented yet?

This is a lot more straight-forward, but still not yet done. 



--
dwmw2

      reply	other threads:[~2001-09-23 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-22 16:09 nftl driver Nikolai Vladychevski
2001-09-23  8:32 ` David Woodhouse
2001-09-24 22:12   ` Nikolai Vladychevski
2001-09-24 23:10     ` David Woodhouse
2001-09-23 15:06 ` jffs2_gcd_mtd4 <defunct> Joakim Tjernlund
2001-09-23 15:12   ` 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=6549.1001257974@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=joakim.tjernlund@lumentis.se \
    --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