From: Thomas Gleixner <tglx@linutronix.de>
To: Kschoo70C@netscape.net, linux-mtd@lists.infradead.org
Subject: Re: Bad Block Handling in jffs2
Date: Thu, 30 Jan 2003 20:16:00 +0100 [thread overview]
Message-ID: <200301302016.00528.tglx@linutronix.de> (raw)
In-Reply-To: <03E2B9D1.52EE4DE7.0265FBE9@netscape.net>
On Thursday 30 January 2003 17:17, Kschoo70C@netscape.net wrote:
> In http://www.linux-mtd.infradead.org/tech/nand.html, it is stated that
>
> "if you have a bad block on your chip, just skip this block and copy
> the data to the next block. JFFS2 is able to handle this gap.".
That's correct.
> So, I write a program to skip the bad block, and copy the data to the
> next block. The missing file seems to appear on the file system now, the
> size looks correct. But when I diff the binary of the file to that of
> original, they are different and the binary failed to execute.
Strange.
Have you built your fs-image with the correct block size ?
> I don't know much about jffs2 bad block handling, the only information I
> have is as mentioned above. Am I missing any other information ?
No
> Is anyone manage to transfer an image to the nand device that has bad
> blocks without losing any files ?
Yes, I do
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2003-01-30 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 16:17 Bad Block Handling in jffs2 Kschoo70C
2003-01-30 19:16 ` Thomas Gleixner [this message]
2003-01-30 20:03 ` kokseng choo
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=200301302016.00528.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=Kschoo70C@netscape.net \
--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 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.