From: Semih Hazar <semih.hazar@indefia.com>
To: linux-mtd@lists.infradead.org
Subject: Strange JFFS2 Cleanmarker on NAND
Date: Fri, 27 Apr 2007 20:08:41 +0300 [thread overview]
Message-ID: <46322E19.7020409@indefia.com> (raw)
Hi,
After testing JFFS2+NAND for a while, I wanted to try summary and some
other stuff, decided to start from scratch.
So I did a flash_eraseall -j and tried to mount it.
But it didn't mount and complained that there wasn't a cleanmaker. So i
did nanddump and saw that there were correct cleanmarkers at the
beginning of the flash, but was some other values beginning from 0x00a80000.
at the beginning:
# nanddump /dev/mtd0 | hexdump -C
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x10000000...
00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|................|
*
00000800 ff ff 19 85 20 03 00 00 00 08 ff ff ff ff ff ff |....
...........|
00000810 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|................|
*
00020fe0 ff ff ff ff ff ff ff ff 19 85 20 03 00 00 00 08 |..........
.....|
00020ff0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|................|
*
00021800 ff ff 19 85 20 03 00 00 00 08 ff ff ff ff ff ff |....
...........|
00021810 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|................|
after 0x00a80000, cleanmarker part was like that:
ff ff 19 85 20 05 00 00 00 18 65 fa fd 45 00 00 |.... .....e..E..|
00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff |................|
ff ff ff ff ff ff ff ff 19 85 20 05 00 00 00 18 |.......... .....|
65 fa fd 45 00 00 00 00 00 00 00 00 00 00 00 00 |e..E............|
I didn't know if this was something meaningful or not, and looked inside
flash_eraseall and didn't see it writing something like that to flash. I
did a flash_eraseall again without -j and did a nanddump everything was
0xff as it should be.
Then did flash_eraseall -j once again, and this time the whole flash was
like that:
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x10000000...
00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|................|
*
00000800 ff ff 19 85 20 05 00 00 00 18 65 fa fd 45 00 00 |....
.....e..E..|
00000810 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
|................|
00000820 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|................|
*
00020fe0 ff ff ff ff ff ff ff ff 19 85 20 05 00 00 00 18 |..........
.....|
00020ff0 65 fa fd 45 00 00 00 00 00 00 00 00 00 00 00 00
|e..E............|
00021000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|................|
*
00021800 ff ff 19 85 20 05 00 00 00 18 65 fa fd 45 00 00 |....
.....e..E..|
00021810 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
|................|
00021820 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
|................|
I re-run the above step (without -j and with -j) and now cleanmarkers
are ok and I can mount it.
Does anyone have any idea what's going on ?
CPU: Atmel AT32AP7000, kernel 2.6.20.
mtd-utils: latest from svn.
Best Regards,
Semih Hazar
next reply other threads:[~2007-04-27 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 17:08 Semih Hazar [this message]
2007-04-28 12:57 ` Strange JFFS2 Cleanmarker on NAND Semih Hazar
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=46322E19.7020409@indefia.com \
--to=semih.hazar@indefia.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