Walkingmind / embox

Automatically exported from code.google.com/p/embox
2 stars 0 forks source link

jffs2 mount failed #678

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. make confload-x86/nonvga_debug and run auto_qemu -hda disk.img
2. root@embox:/#mkdir /mnt
3. root@embox:/#mkfs -t jffs2 /dev/hda
4. root@embox:/#mount -t jffs2 /dev/hda /mnt

What is the expected output? What do you see instead?

<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 
0x3ceb instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004: 
0x4545 instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008: 
0x4545 instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c: 
0x0402 instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010: 
0x0002 instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014: 
0xf840 instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018: 
0x003f instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000028: 
0xf7db instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000002c: 
0x424d instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000030: 
0x445f instead
<5>Further such events for this erase block will not be printed
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00008200: 
0x522f instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00008204: 
0x2054 instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00008208: 
0x2020 instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00008210: 
0x3411 instead
<5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00008218: 
0x3411 instead
<5>Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
<5>empty_blocks 0, bad_blocks 0, c->nr_blocks 2048
tish: mount: Command returned with code -5: I/O error

Original issue reported on code.google.com by alexkalmuk@gmail.com on 30 Jan 2014 at 10:35

GoogleCodeExporter commented 9 years ago
Seems to be fixed for long time

Original comment by drakon.m...@gmail.com on 3 Mar 2015 at 4:12