All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Deschamps <mathieu.deschamps@com2gether.net>
To: David Jander <david.jander@protonic.nl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: How to quickly write cleanmarkers to jffs2 partitions?
Date: Fri, 3 Mar 2006 10:08:20 +0100	[thread overview]
Message-ID: <200603031008.20075.mathieu.deschamps@com2gether.net> (raw)
In-Reply-To: <200603021706.14618.david.jander@protonic.nl>

On Thursday 02 March 2006 17:06, David Jander wrote:
> Hi,
>
> I was wondering if there is a trick or common technique I am ignoring to
> make this more efficient:
>
> This is for a 2.4 kernel based system.
> In production we use either u-boot or a NFS mounted linux system to erase
> flash and write jffs2 partitions to it. The jffs2 images are small (not
> padded to full partition size to save programming time), but the partitions
> are rather big (12 Mbyte in one case). Problem is that when booting for the
> first time, one has to wait several minutes (during which the system is
> more or less useless and busy) to get all cleanmarkers written to flash by
> the jffs2 gc thread. This huge delay is rather unacceptable for production,
> so we are looking for a work-around.
>
> One option would be to make jffs2 images that are padded to full partition
> size, but that also isn't very efficient, considering the image is only
> about 100k in beginning and the partition is 12 Mbyte in size. That would
> take a lot of time programming flash (less time than having the jffs2
> driver fix this nevertheless).
>
> Another option is making a little program that writes cleanmarkers in every
> eraseblock starting from the first completely empty one in a partition
> before mounting that partition for the very first time after flashing.
>
> Since this seems to me like a common situation, I'd like to know if anybody
> knows about a better solution, or if anybody has already dealt with this
> before.
>
> Greetings,


Hi,

"When preparing a flash partition for JFFS2, it is recommended to put 
cleanmarkers to the erased blocks.
This might be done my means of "-j" option of the "flash_eraseall" MTD 
utility. Otherwise, JFFS2 will re-erase the blocks
which contain all 0xFF and have no cleanmarker. This is an unneeded wasting of 
time."

Source : http://www.linux-mtd.infradead.org/faq/jffs2.html

does this may be relevant ?



Best Regards,


Mathieu Deschamps.

  parent reply	other threads:[~2006-03-03  9:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 16:06 How to quickly write cleanmarkers to jffs2 partitions? David Jander
2006-03-02 17:07 ` Jaap-Jan Boor
2006-03-03  9:08 ` Mathieu Deschamps [this message]
2006-03-06 12:21   ` Jaap-Jan Boor
2006-03-08  8:38     ` David Jander
2006-03-10 17:10       ` Jaap-Jan Boor

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=200603031008.20075.mathieu.deschamps@com2gether.net \
    --to=mathieu.deschamps@com2gether.net \
    --cc=david.jander@protonic.nl \
    --cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.