public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Kschoo70C@netscape.net
To: linux-mtd@lists.infradead.org
Subject: Bad Block Handling in jffs2
Date: Thu, 30 Jan 2003 11:17:34 -0500	[thread overview]
Message-ID: <03E2B9D1.52EE4DE7.0265FBE9@netscape.net> (raw)

Hi,
   My nand device has a few bad blocks. Therefore if I copy the jffs2 formated 
   image to the device, some files are missing from the file systems.
 
   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.".

   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.

   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 ?

   Is anyone manage to transfer an image to the nand device that has bad blocks 
   without losing any files ?

   Note that there is no problem to copy the same image to nand devices 
   which are bad blocks free 

   Thanks in advance.

regards
choo


__________________________________________________________________
The NEW Netscape 7.0 browser is now available. Upgrade now! http://channels.netscape.com/ns/browsers/download.jsp 

Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/

             reply	other threads:[~2003-01-30 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-30 16:17 Kschoo70C [this message]
2003-01-30 19:16 ` Bad Block Handling in jffs2 Thomas Gleixner
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=03E2B9D1.52EE4DE7.0265FBE9@netscape.net \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox