All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: rednoah <rednoax@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Bad blocks in a FAT32 partition of MLC nand flash
Date: Mon, 26 Jul 2010 07:52:35 +0300	[thread overview]
Message-ID: <1280119955.14917.11.camel@localhost> (raw)
In-Reply-To: <AANLkTim8PxP47Kor9Ryg8vup_h-s1g2x9fkFI4WlBBhP@mail.gmail.com>

On Thu, 2010-07-22 at 21:37 +0800, rednoah wrote:
> Hi:
>    I'm using samsung s3c2416 board with a 8G MLC nand flash.A partition
> larger than 7G was reserved for cutomer.They use PC to store files in this
> partition.Since Windows XP was their mainly used OS,there is no other
> file-system choice except FAT32.But FAT32 can't cope with bad blocks in
> nand flash,which may be an easy job for yaffs.So these errors such as
> "path too deep","crc error" are common when copying files to the MLC
> nand flash partition.I refered to the mtd homepage.It seems that there is 2
> solutions:
> 
> 1.use a flash translation layer to deal with wear leveling and bad block.But
> it seems that there is no reliable open source FTL for nand flash.There is no
> FTL for MLC nand flash in main-line kernel.
> 
> 2.use ubi layer,but there is no block device driver on ubi for building FAT32
> or ext2.There is a ubi block device driver.But it doesn't belong main-line mtd
> driver.

There is not public upstream solution for your problem. But you can
develop an FTL layer on top of UBI.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2010-07-26  4:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 13:37 Bad blocks in a FAT32 partition of MLC nand flash rednoah
2010-07-26  4:52 ` Artem Bityutskiy [this message]

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=1280119955.14917.11.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rednoax@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.