From: David Woodhouse <dwmw2@infradead.org>
To: Dvir Oren <dviro@lucidvon.com>
Cc: mtd@infradead.org
Subject: Re: Bad Block Table
Date: Tue, 28 Mar 2000 13:52:13 +0100 [thread overview]
Message-ID: <18850.954247933@devel2.axiom.internal> (raw)
In-Reply-To: <38E09EA9.C60FB1CD@lucidvon.com>
dviro@lucidvon.com said:
> 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?
Not yet. That'll come when it handle async erases properly - and keeps a queue
of preerased blocks which are available for writing, rather than going
trawling for a new one each time it needs one.
dviro@lucidvon.com said:
> Could this explain why I'm getting file system trashes?
If you've got bad blocks of flash, yes. It's more likely that I'm just
violating some of the timing requirements for the DiskOnChip, though.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-03-28 12:52 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
2000-03-28 12:52 ` David Woodhouse [this message]
-- 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=18850.954247933@devel2.axiom.internal \
--to=dwmw2@infradead.org \
--cc=dviro@lucidvon.com \
--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