public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Kyle Harris <kharris@nexus-tech.net>
To: Oron Ogdan <Orono@m-sys.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Dvir Oren <dvir@lucidvon.com>, MTD <mtd@infradead.org>
Subject: Re: Questions about MTD
Date: Mon, 20 Mar 2000 11:17:22 -0500	[thread overview]
Message-ID: <38D64F12.C11D7F06@nexus-tech.net> (raw)
In-Reply-To: B17893052A17D211A9860060978F7E63014A0542@mail.msys.co.il



Oron Ogdan wrote:
> 
> Kyle Harris Wrote :
> > I've seen reference to "saving the bad block table" in a couple of
> > places now. It seems that the file system should be able to
> > dynamically
> > create/maintain the bad block table. Is this not true?
> >
> No It's not true, The Bad Block table is static and should not change
> during the life cycle of the device. Just think of the possibility of
> a power failure during the update to this table.
> 
> When talking about new bad blocks that occur during the life cycle of the
> device, it is very
> hard to determine when a new "bad block" is really bad. Just think of
> situations such as power down, Noisy hardware etc. Our philosophy now
> (in M-Systems) is marking new bed blocks only in the copy of the bad
> block table that resides in RAM. So further writes to this block will be
> prevented until the next reset.
> 
> In the next reset, Either the block is bad and then the first write
> will fail again and further writes will be prevented, Or it's good and
> then can be reused.

So will the device still work if the static table has been deleted?

Kyle.


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-03-20 16:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20 14:11 Questions about MTD Oron Ogdan
2000-03-20 16:17 ` Kyle Harris [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-21 12:36 Oron Ogdan
2000-03-20 20:51 Oron Ogdan
2000-03-20 20:51 Oron Ogdan
2000-03-21  2:59 ` Kyle Harris
2000-03-20 19:34 Dvir Oren
2000-03-21  9:01 ` David Woodhouse
2000-03-20 11:17 Oron Ogdan
2000-03-20 13:51 ` Kyle Harris
2000-03-18 20:05 Dvir Oren
2000-03-20  9:41 ` David Woodhouse
2000-03-20 18:06 ` Bill Roman
2000-03-20 18:49   ` David Woodhouse

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=38D64F12.C11D7F06@nexus-tech.net \
    --to=kharris@nexus-tech.net \
    --cc=Orono@m-sys.com \
    --cc=dvir@lucidvon.com \
    --cc=dwmw2@infradead.org \
    --cc=mtd@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