public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Sudeep K N" <sudeepholla.maillist@gmail.com>
To: Sameer <x0081444@ti.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 mount problem on NAND flash
Date: Thu, 3 Jan 2008 19:04:12 +0530	[thread overview]
Message-ID: <366f00c80801030534i30aa3083hb01f00549152b1f6@mail.gmail.com> (raw)
In-Reply-To: <00dc01c84e0b$b10fab20$ec8818ac@ent.ti.com>

Hi,

Try using the -j option with erase:
 ./flash_eraseall -j /dev/mtd8
If it still doesn't work, and its fine with SOFT_ECC, then
there is some problem with spare(oob) only write.

-- 
Regards,
Sudeep

On Jan 3, 2008 6:52 PM, Sameer <x0081444@ti.com> wrote:
> Hi,
> I am working on omap based board with 16bit, small page Samsung NAND of size 64MB.
> I have enabled hardware ecc functionality in the driver code. To test the functionality I run the
> Following tests.
> 1. When the kernel comes up, >>cat /proc/mtd
>         mtd0: 00040000 00020000 "bootloader"
>         mtd1: 00020000 00020000 "params"
>         mtd2: 00200000 00020000 "kernel"
>         mtd3: 03da0000 00020000 "filesystem"
>         mtd4: 00080000 00004000 "NAND-X-Loader"
>         mtd5: 00080000 00004000 "NAND-U-Boot"
>         mtd6: 00040000 00004000 "NAND-U-Boot Environment"
>         mtd7: 00400000 00004000 "NAND-Kernel"
>         mtd8: 03ac0000 00004000 "NAND-File System"
> 2. I erase the NAND flash filesystem partition
>         ./flash_eraseall /dev/mtd8
>         This function passes. I have verified the erase functionality using the debugger.
> 3  mount -t jffs2 /dev/mtdblock8 /mnt/nand. I have enabled the low level jffs2 fs debugging
>         Following is the error message
>
>         JFFS2: Erase block at 0x00000000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x00004000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x00008000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x0000c000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x00010000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x00014000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x00018000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x0001c000 is not formatted. It will be erased
>                                              -----
>                                                 =----
>                                         upto--
>
>         JFFS2: Erase block at 0x03a9c000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x03aa0000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x03aa4000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x03aa8000 is not formatted. It will be erased
>         FFS2: Erase block at 0x03aac000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x03ab0000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x03ab4000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x03ab8000 is not formatted. It will be erased
>         JFFS2: Erase block at 0x03abc000 is not formatted. It will be erased
>         Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
>         mpty_blocks 0, bad_blocks 0, c->nr_blocks 3760
>         mount: Mounting /dev/mtdblock8 on /mnt/nand failed: Input/output error
>
> But when I enable the SW_ECC functionalilty I am able to mount the jffs2 fs and perform the fs operations
>
> I am beginner for JFFS2 fs.Could you please let me know what causes this error.
>
>
> Regards,
> -Sameer
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>

  reply	other threads:[~2008-01-03 13:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AchOC7Aeq8/iWL2SSKmE/WuZCJ0fIw==>
2008-01-03 13:22 ` JFFS2 mount problem on NAND flash Sameer
2008-01-03 13:34   ` Sudeep K N [this message]
2008-05-07 10:26   ` Ram

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=366f00c80801030534i30aa3083hb01f00549152b1f6@mail.gmail.com \
    --to=sudeepholla.maillist@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=x0081444@ti.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