public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Dvir Oren <dviro@lucidvon.com>
To: David Woodhouse <dwmw2@infradead.org>, MTD <mtd@infradead.org>
Subject: Re: Bad Block Table
Date: Tue, 28 Mar 2000 11:59:38 +0000	[thread overview]
Message-ID: <38E09EA9.C60FB1CD@lucidvon.com> (raw)
In-Reply-To: 17860.954236260@devel2.axiom.internal

David Woodhouse wrote:
> dviro@lucidvon.com said:
>  3.  And if the driver is responsible for this, does the 
> MTD driver do the same?
> 
> Not yet.

But does MTD even care about the BadBlockTable?  That is, does nftl.c
check that the block that is about to be written to is not in the bad
block table?

If not, then I guess there is no point in restoring the bad block table
when using the MTD drivers, since they don't care about it anywy.  On
the other hand, nftl_format reconstructs the bad block table anyway.

Could this explain why I'm getting file system trashes?

-- 
Dvir Oren               <dviro@lucidvon.com>
Lucid VON Ltd.     <http://www.lucidvon.com>
9 Saloniki St.,        Tel-Aviv       Israel
Tel:  +972 3 644 3038  Fax:  +972 3 644 3039


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

  parent reply	other threads:[~2000-03-28 11:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-28  9:09 Bad Block Table Dvir Oren
2000-03-28  9:37 ` David Woodhouse
2000-03-28 11:44   ` Dvir Oren
2000-03-28 11:59   ` Dvir Oren [this message]
2000-03-28 12:52     ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2000-04-04 14:55 Dvir Oren
2000-03-26 14:21 Dvir Oren

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=38E09EA9.C60FB1CD@lucidvon.com \
    --to=dviro@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