jffs2常见问题

转载 2017年01月23日 14:44:50

Question1:JFFS2 error: (1) jffs2_build_inode_pass1: child dir "alsa" (ino #1159) of dir ino #1074 appears to be a hard link 
JFFS2 error: (1) jffs2_build_inode_pass1: child dir "l" (ino #1170) of dir ino #1075 appears to be a hard link 
原由 : flash没有erase彻底.  

VFS: Mounted root (jffs2 filesystem) on device 31:1. Freeing init memory: 136K 
JFFS2 notice: (1) check_node_data: wrong data CRC in data node at 0x0f0a7f78: read 0x4462b066, calculated 0x48ea177f. 
JFFS2 error: (488) jffs2_do_read_inode_internal: Argh. Special inode #139 with mode 0x61b0 had more than one node iget() failed for ino #139 mknod: /dev/null: File exists 
Populating /dev using udev: udevd (499): /proc/499/oom_adj is deprecated, please use /proc/499/oom_score_adj instead. 
JFFS2 error: (500) jffs2_do_read_inode_internal: Argh. Special inode #1123 with mode 0x21b0 had more than one node iget() failed for ino #1123     


Question2:jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024: 0x2b10 instead  
mkfs.jffs2 -s 的参数问题 对照FLASH的大小再重新生成镜像文件过即可 The answer this means that the data on your flash device is not a valid JFFS2 file system. 
There is no single solution for this problem, but we will try to provide you some ideas how to fix this.  
The first question you should try to answer is "why the data on my flash device is incorrect so that JFFS2 rejects to deal with it?". There are may be a plenty of reasons, e.g.:  
1. you flash driver is severely buggy so it reads trash instead of valid data;  

2. you flashed some trash instead of a valid JFFS2 image;  
3. you did not manage to flash JFFS2 image correctly so that you ended up with 
garbage on your flash, although the original image was perfectly fine; 

 4. you forgot to erase your flash before flashing it, etc.



Anyways, JFFS2 wouldn't complain if it was able to find correct data. As it does complain, there is something wrong with the data it reads.  
One common mistake is to use /dev/mtdX or /dev/mtdblockX devices to flash JFFS2 images on NAND flashes. E.g.  
cp jffs2_fs.img /dev/mtd2  
This is incorrect because when dealing with NAND flashes one has to skip bad 
eraseblocks and write only in NAND page size chunks. Please, use the nandwrite utility instead.  
Also please, do not forget to erase your flash before flashing the image. You may use the 
flash_eraseall utility for this. And it makes sense to make sure the erase functionality 
actually works by reading the erased MTD device back and checking that only 0xFF bytes were read.  
You may try to check if your flash driver works correctly and if you flashed the file system image correctly by means of reading the flash back after you have flashed your image, and compare the read image with the original one. Please, use the nandread utility to read from NAND flashes.  
You can also do the following experiment to make sure JFFS2 works well. Erase your MTD device and mount it to JFFS2. You will end up with an empty file system. Copy some files to the JFFS2 file system and unmount it. Then mount it again and see if it mounts without problems. If it does, this is most probably not a JFFS2 bug.  

 
Question3:Empty flash at 0xXXXXXXXX ends at 0xXXXXXXXX 
This message is generated if a block of data is partially written. It is generally not a sign of any problem.  

Question4:Name CRC failed on node at 0x00b620c8: Read 0x640c8ca3, calculated 0x795111fe 
重启,则不会有如上CRC错误信息。 问题原因: 
我在烧写jffs2 img之前,使用fis init -f 来擦除flash。fis init -f 命令执行完以后,flash空间就都是0xFF了!即使在mkfs.jffs2的时候使用'-p'参数指定最终输出img的大小,但是超出文件系统的部分也会被填充为0xFF!但这可不是jffs2的格式! 
我用fis create分了5M多(0x590000)的分区,但是jffs2fs.img只有不到3M(0x250000),那么把它烧写到flash以后,分区中除了jffs2 img之外剩余的flash空间(大概2M)全是0xFF,这不是jffs2要求的格式,所以,会发出CRC错误的信息。假如有一种工具,他可以将flash  format为jffs2的格式,那么就不会出现这个问题了。目前我还没有找到这种工具,但是,可以确信的是:上面的CRC错误是不影响jffs2文件系统的使用 
http://blog.chinaunix.net/space.php?uid=20727076&do=blog&id=1885384

Question5: VFS: Mounted root (jffs2 filesystem) readonly.  
Freeing unused kernel memory: 304k freed  Error -3 while decompressing!  804878c4(1884)->81200000(16384)  
Failed to execute /linuxrc. Attempting defaults...  
Kernel panic - not syncing: No init found. Try passing init= option to kernel.  
原由 : 没有仔细看 mkfs.jffs2 的手册, 须要指定-b参数, 大小与PAGE_SIZE一样 (查看.config文件 CONFIG_PAGE_SIZE_16KB=y). 

Question6: 
共提示以下几种错误: 
Empty flash at 0x00258c88 ends at 0x00258c8c 
jffs2_scan_inode_node(): CRC failed on node at 0x002873f0: Read 0x50dc72ec, calculated 0xafbffd1d 
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x002d24ac: 0x000d instead JFFS2 notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. VFS: Mounted root (jffs2 filesystem). Freeing init memory: 124K 
JFFS2 notice: (1) check_node_data: wrong data CRC in data node at 0x00012000: read 0x1a9bfab2, calculated 0xdc27bef6. 
JFFS2 notice: (728) read_dnode: wrong data CRC in data node at 0x0000e438: read 0x3dcf6001, calculated 0xcb81f1ee. 
JFFS2 warning: (1) jffs2_do_read_inode_internal: no data nodes found for ino #14 JFFS2 notice: (1) jffs2_do_read_inode_internal: but it has children so we fake some modes for it 
Failed to execute /linuxrc. Attempting defaults... 
Kernel panic - not syncing: No init found. Try passing init= option to kernel. 分析: 
记得JFFS2是采用自己的ECC算法,但是在内核中又打开了S3C2410_HARDWARE_ECC 解决方案: 去掉硬件ECC

相关文章推荐

jffs2

为方便学习放在这里,感谢作者   声明 你可以自由地随意修改本文档的任何文字内容及图表,但是如果你在自己的文档中以任何形式直接引用了本文档的任何原有文字或图表并希望发布你的文档,那么你也得保证让...

编译内核错误收集

1.Empty flash at 0x0048e234 ends at 0x0048e800 Empty flash at 0x030a94a0 ends at 0x030a9800 JFFS2 ...

JFFS2 文件系统移植

JFFS2 文件系统移植

CComboBox选中

CComboBox CommPortControl;CommPort是其绑定的值,  在初始化函数OnInitDialog里面对CommPortControl赋值完毕后,想把其置为选中状态,但是始终不...
  • zanget
  • zanget
  • 2009年01月11日 20:29
  • 3432

JFFS2 error: (1) jffs2_build_inode_pass1: child dir "udhcpc" (ino #440) of dir ino #336 appears to be a hard link

JFFS2 error: (1) jffs2_build_inode_pass1: child dir "udhcpc" (ino #440) of dir ino #336 appears to b...
  • zanget
  • zanget
  • 2009年04月04日 10:51
  • 2715

[JFFS2文件系统问题(未解决)]Empty flash at 0x012dbffc ends at 0x012dc000

1、Empty flash at Empty flash at ......Empty flash at 0x012dbffc ends at 0x012dc000 //很多JFFS2 notice:...

[转]JFFS2源代码情景分析Beta2

2007-04-29 14:56 2720人阅读 评论(1) 收藏 举报  为方便学习放在这里,感谢作者   声明 你可以自由地随意修改本文档的任何文字内容及图表,但是如果你在自己的文档中...

如何在AT91RM9200上移植jffs2文件系统

我的平台CPU:AT91RM9200;SDRAM:32M;Nor Flash:16M; 1.制作mtd-util工具  (1)从我的资源(http://download.csdn.net/source...
  • jbnie
  • jbnie
  • 2009年03月22日 21:59
  • 1811

文件系统编译过程中遇到问题,解决过程Kernel panic - not syncing: Attempted to kill init!

用4.4.3 编译器编译出来的文件系统 Empty flash at 0x0214bf7c ends at 0x0214c000 Empty flash at 0x0214fffc ends at...

jffs2

 第1章   jffs2在flash上的資料實體及其內核描述符jffs2在flash上只有兩種類型的資料實體:jffs2_raw_inode和jffs2_raw_dirent,其中jffs2_raw_...
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:jffs2常见问题
举报原因:
原因补充:

(最多只允许输入30个字)