From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: "Phillips, Owain" <owain.phillips@siemens.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Flash_eraseall -j and cowardly refusing to mount
Date: Mon, 7 Jan 2008 06:40:51 -0600 [thread overview]
Message-ID: <20080107064051.457d89a1@zod.rchland.ibm.com> (raw)
In-Reply-To: <4B760ED6D70BBC4EBFC0AEFDAFB2392A0AEB9FBC@NTHT202E.siemenscomms.co.uk>
On Mon, 07 Jan 2008 12:16:45 +0000
"Phillips, Owain" <owain.phillips@siemens.com> wrote:
> Hi linux-mtd@lists.infradead.org,
>
> We just upgraded to mtd-utils-1.0.1 on our 2.6.23 target and I am getting
> problems with flash_eraseall -j where the mount fails.
>
> # flash_eraseall -j /dev/mtd11
> Erasing 128 Kibyte @ e20000 -- 36 % complete. Cleanmarker written at e20000.
> Skipping bad block at 0x00e40000
> Erasing 128 Kibyte @ 26a0000 -- 99 % complete. Cleanmarker written at
> 26a0000.
> # mount -t jffs2 /dev/mtdblock11 /mnt
> Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
> empty_blocks 0, bad_blocks 1, c->nr_blocks 310
> mount: Mounting /dev/mtdblock11 on /mnt failed: Input/output error
>
>
> If I do a flash_eraseall without the -j option the mount is OK.
> Is it OK to revert to just doing this non-jffs2-aware erase; what are
> implications/side effects?
>
> If I look at the differences in the filesystems generated via the
> flash_eraseall -y and a flash_eraseall followed by a mount the clean marker
> appears to be different; is that the problem.
>
> First oob for a flash_erase -j.....
>
> 0x000007e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0x000007f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> OOB Data: ff ff 85 19 03 20 08 00 00 00 ff ff ff ff ff ff
> OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>
> First oob for a flash_erase, followed by jffs2 mount....
>
> 0x000007e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0x000007f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> OOB Data: ff ff 85 19 03 20 08 00 00 00 00 00 00 00 ff ff
> OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>
> Here are details for our device.
>
> # mtd_debug info /dev/mtd11
> mtd.type = MTD_NANDFLASH
> mtd.flags =
> mtd.size = 40632320 (38M)
> mtd.erasesize = 131072 (128K)
> mtd.oobblock = 2048 (2K)
> mtd.oobsize = 64
> mtd.ecctype = (unknown ECC type - new MTD API maybe?) regions = 0
> #
>
>
> Any help in pointing out the error of my ways would be greatly appreciated.
> Does it look like we cocked up building the mtd utils?
No. I think the -j option to flash_eraseall is broken. It should
either be fixed or removed.
josh
next prev parent reply other threads:[~2008-01-07 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 12:16 Flash_eraseall -j and cowardly refusing to mount Phillips, Owain
2008-01-07 12:40 ` Josh Boyer [this message]
2008-01-07 15:00 ` David Woodhouse
2008-01-07 18:39 ` Jeff Hane
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=20080107064051.457d89a1@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linux-mtd@lists.infradead.org \
--cc=owain.phillips@siemens.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