From: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>
To: <mtd@infradead.org>
Subject: mkfs.jffs2 again
Date: Thu, 19 Apr 2001 15:44:35 +0200 [thread overview]
Message-ID: <000e01c0c8d6$dfb791c0$0a01a8c0@Win1> (raw)
In-Reply-To: <1991.987680017@redhat.com>
If I run mkfs.jffs2 on my PC(rh 7) I get this
when I mount it on my RPX(PPC860) board:
sh-2.03# mount -t jffs2 /dev/mtdblock0 mtdblock0/
mtdblock_open
ok
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000:
0x8519 inst
ead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004:
0x4400 inst
ead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008:
0x1dfb inst
ead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c:
0x0100 inst
ead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010:
0x0100 inst
ead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014:
0xed41 inst
ead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020:
0xf4de inst
ead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024:
0x9bde inst
ead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000028:
0x9bde inst
ead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000040:
0xfc56 inst
ead
Further such events for this erase block will not be printed
JFFS2: Erase block at 0x00000000 is not formatted. It will be erased
JFFS2: Erase block at 0x00008000 is not formatted. It will be erased
JFFS2: Erase block at 0x00010000 is not formatted. It will be erased
JFFS2: Erase block at 0x00018000 is not formatted. It will be erased
JFFS2: Erase block at 0x00020000 is not formatted. It will be erased
JFFS2: Erase block at 0x00028000 is not formatted. It will be erased
JFFS2: Erase block at 0x00030000 is not formatted. It will be erased
JFFS2: Erase block at 0x00038000 is not formatted. It will be erased
Then if I run mkfs.jffs2 on my RPX board I only get a few:
JFFS2: Erase block at 0x00000800 is not formatted. It will be erased
which I think is normal.
Can this be an big/little endian issue?
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-04-19 13:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 9:21 cramfs and mtd Bjorn Wesen
2001-04-19 11:33 ` David Woodhouse
2001-04-19 13:44 ` Joakim Tjernlund [this message]
2001-04-19 13:52 ` mkfs.jffs2 again David Woodhouse
2001-04-19 13:56 ` Joakim Tjernlund
2001-04-19 20:06 ` JFFS2 as root FS Joakim Tjernlund
2001-04-20 16:26 ` David Woodhouse
2001-04-21 8:07 ` Joakim Tjernlund
2001-04-21 11:22 ` David Woodhouse
2001-04-21 20:22 ` Joakim Tjernlund
2001-04-23 1:52 ` David Schleef
2001-04-23 6:15 ` Joakim Tjernlund
2001-04-23 9:28 ` Joakim Tjernlund
2001-04-23 9:31 ` David Woodhouse
2001-04-23 11:00 ` David Schleef
2001-04-23 11:04 ` David Woodhouse
2001-04-24 1:56 ` David Schleef
2001-04-21 12:08 ` David Woodhouse
2001-04-21 20:14 ` Joakim Tjernlund
2001-04-21 22:18 ` 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='000e01c0c8d6$dfb791c0$0a01a8c0@Win1' \
--to=joakim.tjernlund@lumentis.se \
--cc=mtd@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