From: "Chuck Meade" <chuckmeade@mindspring.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: RE: DOC filesystem questions
Date: Thu, 7 Aug 2003 12:09:32 -0400 [thread overview]
Message-ID: <IIEEICKJLNEPBBDJICNGOEHADMAA.chuckmeade@mindspring.com> (raw)
In-Reply-To: <1060252989.25209.39.camel@passion.cambridge.redhat.com>
David Woodhouse wrote:
> > Also I am concerned from what I have read in the archives about
> > the bad block table. From what I see in the archives and in
> > Karim Yaghmour's book, I needed to save this off. Unfortunately
> > however I cannot run DOS or its utilities on this target board,
> > so I don't think that there is any way to do this.
>
> You can read from /dev/mtd0 after first loading the DiskOnChip driver.
> It's in there somewhere (see the NFTL and nftl_format code for more
> details of precisely where). In fact, you could probably hack nftldump
> to dump it, quite easily.
It looks like nftldump sees the bad unit table as being the 7680
bytes starting at byte offset 512 into the device. So this would
certainly be possible. After looking more closely at nftl_format
I don't know if it is absolutely necessary to save it though:
nftl_format actually creates a bad unit table at offset 512
beyond the offset that the user provides on the command line. The
size of the bad unit table it creates is based on the actual number
of erase units in the device, so I suppose it will not always be
7680. It looks for blocks marked bad in their oob data to create
this table. It also (by default) will do read/write/erase checking
on each block not already marked bad in its oob data, and any
failures are added to the bad unit table as well.
So it seems the news isn't that bad. If we always leave the oob
data alone when the oob is marked bad for a block at the factory,
then nftl_format will include it in the BadUnitTable it creates.
Then preserving the factory-set bad block table would only be
critical if it marks blocks bad that are not marked bad in their
oob data.
Is this correct? It appears that nftl_format is already doing
a good job of preserving bad block data, at least that which comes
from the oob data and r/w/e testing.
> > I use the following commands:
> >
> > nftl_format /dev/mtd0
> > fdisk /dev/nftla
>
> Not without 'insmod nftl' or 'reboot -f' between them, I hope.
You are correct. I missed entering that line as I transcribed
my notes. There is an 'insmod nftl' between those 2 lines in
the command sequence that I used.
> > 3. What I would really prefer to use is JFFS2 on this DOC.
> > I have seen messages from David that this may now be
> > possible.
>
> It's becoming possible. Give me a few weeks.
That is great news!
Thanks,
Chuck
next prev parent reply other threads:[~2003-08-07 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 4:27 DOC filesystem questions Chuck Meade
2003-08-07 10:43 ` David Woodhouse
2003-08-07 16:09 ` Chuck Meade [this message]
2003-08-07 16:32 ` David Woodhouse
2003-08-07 16:56 ` Chuck Meade
2003-08-08 7:30 ` David Woodhouse
2003-08-08 13:42 ` Chuck Meade
2003-08-08 14:05 ` David Woodhouse
2003-09-19 22:27 ` Chuck Meade
2003-09-20 1:20 ` Chuck Meade
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=IIEEICKJLNEPBBDJICNGOEHADMAA.chuckmeade@mindspring.com \
--to=chuckmeade@mindspring.com \
--cc=dwmw2@infradead.org \
--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