RE: JFFS2 Cleanmarker issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Suresh,

Sorry for the delayed response. I was on leave for 3 days. 

Vinod had solved this problem when we were working in SMI. This has got
something to do with the way you generate the jffs2 image (some command line
parameter) and writing the image with nandwrite.

He will be able to help you.

Regards,
Praveen.

-----Original Message-----
From: Suresh Rajashekara [mailto:rajashekara.suresh@xxxxxxxxx] On Behalf Of
Suresh Rajashekara
Sent: Friday, June 13, 2008 6:52 AM
To: linux-omap@xxxxxxxxxxxxxxx
Subject: JFFS2 Cleanmarker issue

Hi Everyone,

Few necessary details before I explain my issue.

Hardware I use: OMAP5912 based board
Linux: 2.6.16-rc3 (rc!!, yes)

Let me know if you guys need more details.

The issue:
I use the JFFS2 file system on the oneNAND flash. Every time I boot the 
board I see the following on the serial console (I have 
CONFIG_JFFS2_FS_DEBUG=2)

<SNIP>
jffs2_check_nand_cleanmarker(): Cleanmarker node not detected in block 
at 00000000
OOB at 00000000 was ff ff 00 19 03 03 ff ff ff ff ff 56 fe ff ff ff ff 
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
jffs_check_nand_cleanmarker returned 1
jffs2_check_oob_empty returned 1
JFFS2: Erase block at 0x00000000 is not formatted. It will be erased
jffs2_check_nand_cleanmarker(): Cleanmarker node not detected in block 
at 00020000
OOB at 00020000 was ff ff 00 19 03 03 ff ff ff ff ff 56 fe ff ff ff ff 
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
jffs_check_nand_cleanmarker returned 1
jffs2_check_oob_empty returned 1
blah..
.
blah...
.
.
</SNIP>

Getting this on the first boot, is I guess expected. But this messages 
repeats every time we reboot the board. I did some debugging and found 
that the JFFS2 driver is marking these blocks and writes the clean markers.

Since these prints were appearing on every boot, I read the oob area 
which the jffs2 driver wrote to mark the cleanmarkers. I found the data 
to be shifted. I tried Googling and also went through the GIT log 
messages to find if this was a known issue, but could not find any. Is 
this a known issue in 2.6.16-rc3.

The developers who did the initial design have chosen to format the 
partition using the nftl_format command. I read on the MTD howto that it 
should not be used. I tried replacing that with "flash_eraseall -j" and 
created the jffs2 file system using the command mkfs.jffs2 (I tried with 
the correct page size and other stuff by looking in to the datasheet) 
and wrote the jffs2 file system using the nand_write command, but none 
helped.

Could someone please point me in the right direction?

Thanks in advance,

Best Regards,
Suresh

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux