From: kokseng choo <Kschoo70C@netscape.net>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: Bad Block Handling in jffs2
Date: Thu, 30 Jan 2003 20:03:59 +0000 [thread overview]
Message-ID: <3E39852F.8020100@netscape.net> (raw)
In-Reply-To: 200301302016.00528.tglx@linutronix.de
Hi Thomas,
Thanks for your reply.
Thomas Gleixner wrote:
>> 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 ?
>
The command I used is as followed:
mkfs.jffs2 -p --eraseblock=16KiB -l -d ./jffsRoot -o jffs2.image
I changed the mkfs.jffs2 so that it allows me to create image with 16KiB
erased size. I presumed it is not a problem to make the changed, but may
be I was wrong. The raised the question about my changes sometimes ago
in http://lists.infradead.org/pipermail/linux-mtd/2002-October/006273.html..
Please let me know, if my assumption is wrong.
>
>
>> Is anyone manage to transfer an image to the nand device that has bad
>>blocks without losing any files ?
>>
>>
>Yes, I do
>
>
>
That sounds a lot more promising. Probably there is somthing wrong my
configuration, I will look into my configuration again.
cheers
choo
prev parent reply other threads:[~2003-01-30 19:25 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
2003-01-30 20:03 ` kokseng choo [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=3E39852F.8020100@netscape.net \
--to=kschoo70c@netscape.net \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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.