From: Holger Schurig <h.schurig@mn-solutions.de>
To: linux-mtd@lists.infradead.org
Subject: behavior of JFFS2 and old data in flash
Date: Mon, 3 Apr 2006 16:41:22 +0200 [thread overview]
Message-ID: <200604031641.22989.h.schurig@mn-solutions.de> (raw)
Is the following statement correct?
When I have an JFFS2 file system which was used for some time
at a customer and now I want to re-flash it, then I have to
erase the whole flash (e.g. all of the 64 MB), even when my
image is only 2.5 MB. Otherwise at the next mount JFFS2 might
intermix sectors from the old image in unerase sectors and
from the new image".
Now, what if I use sumtool? AFAIK sumtool stores the erase sectors
inside an the image. Now JFFS2 knows where erased sectors are located
and doesn't scan the whole image. Therefore the old garbage in the
not-erased-sectors should't make a problem.
If this statement is true as well, then I could omit the
tediuous/time-consuming blockwise erase (my chips don't have a
erase-the-whole-chip function).
reply other threads:[~2006-04-03 15:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200604031641.22989.h.schurig@mn-solutions.de \
--to=h.schurig@mn-solutions.de \
--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