* JFFS2 strange behaveour
@ 2004-03-01 15:48 Gerrit Van de Velde
2004-03-01 16:05 ` David Woodhouse
0 siblings, 1 reply; 3+ messages in thread
From: Gerrit Van de Velde @ 2004-03-01 15:48 UTC (permalink / raw)
To: linux-mtd
Hello,
I've made a JFFS2 image from my root filesystem to use in an embedded
platform (Motorola MPC5200). Everything works, i can mount it when burnt
into flash but when I switch from root filesystem on NFS to the image
which resides in FLASH, I get following strange errors during startup:
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 == 0xd00000, free_chunk_size2 ==
0x0, fmc->free_size == 0x0
JFFS: Failed to mount device 1f:02.
VFS: Mounted root (jffs2 filesystem).
So JFFS states: mount failed,
VFS states: mount successful...
after that i get the login prompt and only after one minute i'm able to
login (don't know why)
after logged in i can retrieve the following information:
# df
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 13312 3920 9392 29% /
/dev/mtdblock2 13312 3920 9392 29% /
# dmesg
<snip>Kernel command line: root=/dev/mtdblock2 rw
ip=192.168.0.3:192.168.0.150:192.168.0.1:255.255.255.0:icecube::off
init=init
<snip>
# cat /etc/fstab
none /proc proc defaults
Does anyone know why df states two mounts on the /
and why the jffs errors occur during startup ?
Kind regards,
Gerrit Van de Velde
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: JFFS2 strange behaveour
2004-03-01 15:48 JFFS2 strange behaveour Gerrit Van de Velde
@ 2004-03-01 16:05 ` David Woodhouse
2004-03-01 16:20 ` Gerrit Van de Velde
0 siblings, 1 reply; 3+ messages in thread
From: David Woodhouse @ 2004-03-01 16:05 UTC (permalink / raw)
To: Gerrit Van de Velde; +Cc: linux-mtd
On Mon, 2004-03-01 at 16:48 +0100, Gerrit Van de Velde wrote:
> I get following strange errors during startup:
> JFFS: Failed to mount device 1f:02.
Nothing strange there. There's no JFFS file system; JFFS fails to mount.
Why did you even build it into your kernel?
JFFS2 works though:
> rootfs 13312 3920 9392 29% /
> /dev/mtdblock2 13312 3920 9392 29% /
That's normal behaviour for recent kernels, whatever the rootfs actually
is.
--
dwmw2
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: JFFS2 strange behaveour
2004-03-01 16:05 ` David Woodhouse
@ 2004-03-01 16:20 ` Gerrit Van de Velde
0 siblings, 0 replies; 3+ messages in thread
From: Gerrit Van de Velde @ 2004-03-01 16:20 UTC (permalink / raw)
To: David Woodhouse; +Cc: linux-mtd
> Nothing strange there. There's no JFFS file system; JFFS fails to mount.
> Why did you even build it into your kernel?
ok !
i rebuilt the kernel with only jffs2 and not both versions in it
all is ok now, thx for the quick response ;)
Kind regards,
Gerrit Van de Velde
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-03-01 16:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-01 15:48 JFFS2 strange behaveour Gerrit Van de Velde
2004-03-01 16:05 ` David Woodhouse
2004-03-01 16:20 ` Gerrit Van de Velde
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.