root jffs2

[Xavier DEBREUIL]

I have managed to mount the jffs2 as root filesystem (yes I know many
did it but I encountered problems here and there...)
Nevertheless, some kernel messages are a little amazing :

(root=1F01 and not root=/dev/mtdblock1...)

...
root_device_name : 1F01
mtdblock_open
ok
mtdblock: read on "cramfs partition" at 0x400, size 0x400
mtdblock: read on "cramfs partition" at 0x0, size 0x1000
mtdblock: read on "cramfs partition" at 0x1000, size 0x1000
mtdblock: read on "cramfs partition" at 0x2000, size 0x1000
mtdblock: read on "cramfs partition" at 0x3000, size 0x1000
wrong magic
JFFS: Trying to mount device 1f:01.
jffs_build_fs()
jffs_create_control()
jffs_scan_flash(): start pos = 0x0, end = 0x300000
check_partly_erased_sector():checking sector which contains offset 0x0
for flipping bits..
check_partly_erased_sector():checking sector which contains offset
0x1000 for flipping bits..
...
blahblah...
...
check_partly_erased_sector():Done checking all sectors till offset
0x300000 for flipping bits.
*************** Dirty flash memory or bad inode: hexdump(pos = 0x0, len
= 128):
0: 8519 02e0 4400 0000 1dfb f798 0100 0000  ...àD....û÷.....
16: 0100 0000 ed41 0000 f501 f501 0000 0000  ....íA..õ.õ.....
32: de1d 1d3b 4228 263b 4228 263b 0000 0000  Þ..;B(&;B(&;....
48: 0000 0000 0000 0000 0000 0000 0000 0000  ................
64: 3c72 4031 8519 01e0 2b00 0000 e66e 267d  <r at 1...à+...æn&}
80: 0100 0000 0200 0000 0200 0000 4228 263b  ............B(&;
96: 0304 0000 5f5a ae8b dee2 4e56 6c69 62ff  ...._Z®.ÞâNVlibÿ
112: 8519 02e0 4400 0000 1dfb f798 0200 0000  ...àD....û÷.....
jffs_scan_flash(): 0xffffffff at pos 0x11afc.
jffs_scan_flash():0xffffffff ended at pos 0x11b00.
Dirty space: Starting 0x11afc for 0x4 bytes
*************** Dirty flash memory or bad inode: hexdump(pos = 0x11b00,
len = 128):
72448: 8519 01e0 3100 0000 1dd9 8242 0200 0000  ...à1....Ù.B....
72464: 0900 0000 0a00 0000 eb1d 1d3b 090a 0000  ........ë..;....
...

seems that many things are dirty though I have never mounted it
before...

...
jffs_scan_flash(): 0xffffffff at pos 0x2e000c.
jffs_scan_flash():0xffffffff ended at pos 0x300000.
Free space (#24) found but *Not* accepted: Starting 0x2e000c for 0x1fff4
bytes
Dirty space: Starting 0x2e000c for 0x1fff4 bytes
jffs_scan_flash(): Did not find even a single chunk of free space. This
is BAD!
jffs_scan_falsh():Free size accounting screwed
jfffs_scan_flash():free_chunk_size1 == 0x300000, free_chunk_size2 ==
0x0, fmc->free_size == 0x0
jffs_cleanup_control()
----> !!!!!
----> JFFS: Failed to mount device 1f:01.
----> VFS: Mounted root (jffs2 filesystem) readonly.
----> !!!!!
Freeing init memory: 48K
serial console detected.  Disabling virtual terminals.
init started:  BusyBox v0.51 (2001.06.05-17:42+0000) multi-call binary


So, on the one hand, it indicates that it failed to mount the device on
1F01 but afterwards, it managed to mount the jffs2 filesystem as root
fs. Is it a known behaviour or do I have to modify some parameters ?

Xavier