public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] JFFS2 problems
@ 2005-06-07 15:26 Stéphane Royo
  2005-06-07 18:06 ` Andrew Lunn
  0 siblings, 1 reply; 2+ messages in thread
From: Stéphane Royo @ 2005-06-07 15:26 UTC (permalink / raw)
  To: ecos-discuss

Hi everybody,

I ported JFFS2 package on my board and i have two problems. The first
concerns the last umount of jffs2_1 test (umount("/")), it always returns
the following error :

Ino #1 has use count 2
<FAIL>: umount() returned -1 Resource busy.

I didn't make any modification on jffs2_1.

I think the second problem is due to garbage collection. When i execute the
jffs2_1 about ten times the following
error appears :

<FAIL>: open() returned -1 No space left on device
ASSERT FAIL: fd.cxx[280]cyg_file* cyg_fp_get() fd out of range
ASSERT FAIL: fd.cxx              [ 280] cyg_file* cyg_fp_get()

and in same way, when i execute the jffs2_3 i have the error :

<5>jffs2_reserve_space(): Low on dirty space to GC, but it's a deletion.
Allowin
g...
FAIL: creat() returned -0000001
ASSERT FAIL: fd.cxx[280]cyg_file* cyg_fp_get() fd out of range
ASSERT FAIL: fd.cxx              [ 280] cyg_file* cyg_fp_get()
                                                             fd out of range

For information, i use the minimal configuration for JFFS2 (no kernel, no
com driver, only lib, JFFS2 package and flash driver) and the
CYGNUM_IO_FLASH_BLOCK_LENGTH_1 is equals to 256kb.

I would like to know if somebody has encountered the same problems.

Thank,
Stephane


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [ECOS] JFFS2 problems
  2005-06-07 15:26 [ECOS] JFFS2 problems Stéphane Royo
@ 2005-06-07 18:06 ` Andrew Lunn
  0 siblings, 0 replies; 2+ messages in thread
From: Andrew Lunn @ 2005-06-07 18:06 UTC (permalink / raw)
  To: St?phane Royo; +Cc: ecos-discuss

On Tue, Jun 07, 2005 at 05:25:50PM +0200, St?phane Royo wrote:
> Hi everybody,
> 
> I ported JFFS2 package on my board and i have two problems. The first
> concerns the last umount of jffs2_1 test (umount("/")), it always returns
> the following error :
> 
> Ino #1 has use count 2
> <FAIL>: umount() returned -1 Resource busy.
> 
> I didn't make any modification on jffs2_1.
> 
> I think the second problem is due to garbage collection. When i execute the
> jffs2_1 about ten times the following
> error appears :
> 
> <FAIL>: open() returned -1 No space left on device
> ASSERT FAIL: fd.cxx[280]cyg_file* cyg_fp_get() fd out of range
> ASSERT FAIL: fd.cxx              [ 280] cyg_file* cyg_fp_get()
> 
> and in same way, when i execute the jffs2_3 i have the error :
> 
> <5>jffs2_reserve_space(): Low on dirty space to GC, but it's a deletion.
> Allowin
> g...
> FAIL: creat() returned -0000001
> ASSERT FAIL: fd.cxx[280]cyg_file* cyg_fp_get() fd out of range
> ASSERT FAIL: fd.cxx              [ 280] cyg_file* cyg_fp_get()
>                                                              fd out of range
> 
> For information, i use the minimal configuration for JFFS2 (no kernel, no
> com driver, only lib, JFFS2 package and flash driver) and the
> CYGNUM_IO_FLASH_BLOCK_LENGTH_1 is equals to 256kb.

How did you manage to compile the tests without the kernel? The second
include statement for jffs2_1.c is <pkgconf/kernel.h>?

What size flash blocks does your target use?

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-06-07 18:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-07 15:26 [ECOS] JFFS2 problems Stéphane Royo
2005-06-07 18:06 ` Andrew Lunn

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).