From: Felix Domke <tmbinc@elitedvb.net>
To: Josh Boyer <jdub@us.ibm.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Incomplete nodes written to flash
Date: Tue, 31 Aug 2004 14:14:40 +0200 [thread overview]
Message-ID: <41346BB0.6030107@elitedvb.net> (raw)
In-Reply-To: <1093953527.25339.70.camel@weaponx.rchland.ibm.com>
Josh Boyer wrote:
>Have you actually lost data? I have seen the case where GC nodes don't
>get flushed to the medium on my board, but I haven't lost data.
>
>
u-boot's jffs2_1pass ignores CRCs (i know, bad behaviour. I should fix
that, or is there any other jffs2 reader avaiable?), and thus prefers
the latest, incomplete version of the file.
>pdflushd will write out non-GC nodes. GC nodes aren't flushed because
>of wasted space with padding I suppose.
>
>
Ok, that sounds good.
I now see that the garbage collection is done to fill up write buffers,
i.e. flush the important data to flash.
Felix
prev parent reply other threads:[~2004-08-31 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 11:22 Incomplete nodes written to flash Felix Domke
2004-08-31 11:58 ` Josh Boyer
2004-08-31 12:14 ` Felix Domke [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=41346BB0.6030107@elitedvb.net \
--to=tmbinc@elitedvb.net \
--cc=jdub@us.ibm.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