From: Artem Bityutskiy <dedekind1@gmail.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Latest mkfs.jffs2 is broken.
Date: Fri, 15 Oct 2010 09:14:05 +0300 [thread overview]
Message-ID: <1287123245.18576.2.camel@localhost> (raw)
In-Reply-To: <0D753D10438DA54287A00B02708426976450C42B27@AUSP01VMBX24.collaborationhost.net>
On Thu, 2010-10-14 at 16:54 -0500, H Hartley Sweeten wrote:
> Hello all,
>
> Buildroot recently bumped the mtd-utils package from version 1.3.1 to 1.4.0.
>
> With the mkfs.jffs2 utility in 1.3.1 I am able to create rootfs.jffs images that
> work fine on my i.mx35 arm system. But, with the 1.4.0 version all the images
> do not work.
>
> With the 1.4.0 built images I get messages like this during the kernel boot:
>
> jffs2_scan_eraseblock(): Node at 0x00000000 {0x1985, 0x2003, 0x0000000c) has invalid CRC 0x813c6fd8 (calculated 0xe41eb0b1)
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004: 0x000c instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008: 0x6fd8 instead
> jffs2_scan_eraseblock(): Node at 0x0000000c {0x1985, 0xe001, 0x0000002b) has invalid CRC 0x1804b18f (calculated 0x7d266ee6)
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010: 0x002b instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014: 0xb18f instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018: 0x0001 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020: 0x0002 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024: 0x1a8d instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000028: 0x0403 instead
> Further such events for this erase block will not be printed
> Old JFFS2 bitmask found at 0x00000078
> You cannot use older JFFS2 filesystems with newer kernels
> Empty flash at 0x0000a46c ends at 0x0000a470
>
> And, if I check the images with jffs2dump I get stuff like:
>
> Wrong hdr_crc at 0x0001f808, 0x783f44d2 instead of 0x1d1d9bbb
> Wrong bitmask at 0x0001f80c, 0x07f3
> Empty space found from 0x0001fffc to 0x00020000
>
> Any ideas what could be wrong with the 1.4.0 release?
Could you please bisect the mtd-utils.git tree and find the offending
commit.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-10-15 6:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 21:54 Latest mkfs.jffs2 is broken H Hartley Sweeten
2010-10-15 6:14 ` Artem Bityutskiy [this message]
2010-10-15 8:35 ` Peter Korsgaard
2010-10-15 8:43 ` Artem Bityutskiy
2010-10-15 8:52 ` Peter Korsgaard
2010-10-16 15:49 ` Artem Bityutskiy
2010-10-16 20:19 ` Peter Korsgaard
2010-10-18 20:51 ` Peter Korsgaard
2010-10-19 4:49 ` Artem Bityutskiy
2010-10-19 8:38 ` Peter Korsgaard
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=1287123245.18576.2.camel@localhost \
--to=dedekind1@gmail.com \
--cc=hartleys@visionengravers.com \
--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;
as well as URLs for NNTP newsgroup(s).