public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Russ Dill <russ.dill@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: squashfs and NAND flash
Date: Fri, 28 Apr 2006 00:35:46 +0100	[thread overview]
Message-ID: <44515552.6040606@lougher.demon.co.uk> (raw)
In-Reply-To: <f9d2a5e10604271433y34b72c19p22bb10c79b305d97@mail.gmail.com>

Russ Dill wrote:
> On 4/25/06, Andy Hawkins <a.hawkins@cabletime.com> wrote:
> 
>>Hi,
>>
>>
>>>Should mtd handle bad blocks when using squashfs?
>>
>>I suspect you will have to write a simple 'translation layer' that
>>automatically skips bad blocks. This is something we had to do in our
>>device.
>>
>>Basically, if (for example) block 4 is bad, then any request for block 4
>>should actually return block 5. Also, any request for block 5 should return
>>block 6 etc. etc. etc.
>>
> 
> 
> Even worse, NAND flash bits occasionally flip for no reason, ie, even
> when the sector isn't bad. If you read a sector, and get an ecc
> correction, you should rewrite the sector to a free sector, and then
> mark the current sector as free.
> 
> So in other words, even with a read only filesystem, you need a good
> FTL, unless you really don't care if units stop booting after a year
> or two.

A couple of years ago I did some work making Squashfs work with NAND. 
Because of the inherent unreliability of NAND, and the constant MTD code 
base changes, I decided not to make this work publically available.

Providing native NAND support in Squashfs represents too much work for 
absolutely no gain.  It is unlikely this is going to change in the near 
future.

Phillip Lougher

  reply	other threads:[~2006-04-27 23:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 10:02 squashfs and NAND flash Anil Gupta
2006-04-25 10:26 ` Andy Hawkins
2006-04-27 21:33   ` Russ Dill
2006-04-27 23:35     ` Phillip Lougher [this message]
2006-04-28  1:06       ` Josh Boyer
2006-04-28 12:12         ` Phillip Lougher
2006-04-28 12:36           ` Josh Boyer
2006-04-25 12:21 ` Vitaly Wool

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=44515552.6040606@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=linux-mtd@lists.infradead.org \
    --cc=russ.dill@gmail.com \
    /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