This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: JFFS2 no space left on device error
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Edgar Grimberg <edgar dot grimberg at rms dot ro>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Sun, 31 Jul 2005 14:33:32 -0600
- Subject: Re: [ECOS] JFFS2 no space left on device error
- References: <42ECFE3A.9060201@rms.ro>
On Sun, 2005-07-31 at 19:37 +0300, Edgar Grimberg wrote:
> Hi,
>
> I have loaded the jffs2 image provided in the eCos tree onto my board
> (EB40A-like) using redboot and the serial port. I made an FIS entry
> named JFFS2 with this image. (no errors so far)
> After that, using the BDI2000 debugger, I have programmed the jffs2_1
> test onto the board.
> It seems that the mounting of the jffs2 image is working OK (at least no
> errors on the serial), I get some directory listing (perhaps not OK,
> considering the file structure from the support/jffs2 folder):
>
> <INFO>: reading directory /
> <INFO>: entry . [mode 016f0001 ino 00000001 nlink 1 size 0]
> <INFO>: entry .. [mode 016f0001 ino 00000001 nlink 1 size 0]
>
> Creating a file gives me:
>
> <INFO>: create file /foo size 202
> <FAIL>: open() returned -1 No space left on device
> <FAIL>: write() returned -1 Bad file handle
>
> and the bad file handle message continues.
>
> Any hints?
When you created the image (in RedBoot), did you make it larger
than the actual JFFS2 image that you created? In other words,
JFFS2 needs additional FLASH space within the RedBoot (FIS)
image in order to create new files (or even rewrite/update
existing ones).
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss