From: "Chuck Meade" <chuckmeade@mindspring.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: RE: DOC filesystem questions
Date: Fri, 19 Sep 2003 18:27:58 -0400 [thread overview]
Message-ID: <IIEEICKJLNEPBBDJICNGEEDIDPAA.chuckmeade@mindspring.com> (raw)
In-Reply-To: <1060327833.25209.271.camel@passion.cambridge.redhat.com>
> On Thu, 2003-08-07 at 17:56, Chuck Meade wrote:
> > David Woodhouse wrote:
> >
> > > We _must_ retain the bad block table which was on the device when it
> > > arrived from the factory.
> >
> > OK I see. Would it be valuable then to have a Linux command-line
> > utility which captures the BBT before calling nftl_format, then
> > is used to restore the BBT after calling nftl_format but before
> > nftl tries to mount any partitions (via 'insmod nftl' or whatever)?
>
> ... or which writes it back as _part_ of the nftl_format process,
> perhaps?
>
> Yes, it would be extremely useful to do this.
I have been working on the utilities to do this. It is working on my
DOC Millennium device that is soldered to the target board. I now
have a requirement to do the same with a DIMM DOC device.
The device has the following markings:
MD-2220-D16-V3
DiskOnChip B-1.21
DIMM (serial number follows)
This device is identified as a DOC 2000 at bootup, while my other one is
identified as a DOC Millennium.
I am starting out saving and restoring the bad block table from the command
line using dd. Since the bad block table is to be saved before the
nftl_format, and restored afterwards, I thought it would be handy to do
it with a shell script that uses dd.
This approach is working on the DOC Millennium device. It is not working,
however, on my DOC 2000 device. I get:
Read of bad sector table failed (err -5)
when I boot after restoring the bad block table via dd.
The -5 is an EIO being returned because it is unhappy with the ECC
that is read out. I modified doc2000.c to print out the ECC codes that
are being written in doc_write_ecc, and read in doc_read_ecc. They
do not match at all.
Is there a known problem with ECC reading/writing with DOC 2000
devices, or a subset of DOC 2000 devices?
Thanks very much,
Chuck Meade
next prev parent reply other threads:[~2003-09-19 22:28 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
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 [this message]
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=IIEEICKJLNEPBBDJICNGEEDIDPAA.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