public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jakub   Bednář" <bednar.jakub@centrum.cz>
To: <linux-mtd@lists.infradead.org>
Subject: NAND flash file system and JFFS2 problem
Date: Thu, 22 Mar 2007 09:26:28 +0100	[thread overview]
Message-ID: <200703220926.22574@centrum.cz> (raw)

Hi,
      I've spent long time reading all about mtd devices and I'd like 
to check if I understood correctly.

1.) The NFTL is usable ONLY for DOC, not for normal NAND flashes.
      Thats why nftl_format prints unrecognized erase size 0x20000

2.) FTL is usable ONLY with NOR flashes, that's why the ftl_format
       ends with an error on trying to erase bad block on NAND in dmesg.

3.) So there should be used JFFS2 on NAND, there is no good and reliable
       way to run ext2 on NAND.

I've also encountered a problem.
        I'm using kernel 2.6.16.20 from buildroot on DBAu1550 like board.
        When running destroy test on Samsung NAND where I had ext2, 
        I was using programs from busybox placed on NOR flash (jffs2) /dev/mtdblock0. 
        Links like dd, cp, md5sum.

        NAND was mounted on /mnt/. After creating a 45MB file /mnt/file0 with dd
        from /dev/zero  and running md5sum, something got wrong and all the links
        from NOR jffs2 stopped working with lot's of errors in CRC codes. I wasnt writting
        to the NOR jffs2 but I have it mounted rw.  After rebooting the NOR jffs2 is ok again!

        So maybe it mess up in RAM???  What can couse this trouble?

Thanks a lot for Your answer

Jakub

             reply	other threads:[~2007-03-22  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  8:26 Jakub   Bednář [this message]
2007-03-22 12:22 ` NAND flash file system and JFFS2 problem Josh Boyer
2007-03-23 12:26 ` 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=200703220926.22574@centrum.cz \
    --to=bednar.jakub@centrum.cz \
    --cc=linux-mtd@lists.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