[ECOS] jffs2 creat file error
Srinivas rao
ch_srinivas321@yahoo.co.in
Mon Oct 16 08:53:00 GMT 2006
Hi,
I enabled jffs2 package on eCos and testing on my board.
My jffs2 is on 11th sector of flash. 'ls" working fine.
After ls, Iam getting error like below
pls provide the information regarding below error
>Eep. Child "ram3" (ino #127) of dir ino #4 doesn't exist!
<INFO>: reading directory /
<INFO>: entry . [mode 016f0001 ino 00000001 nlink 1 size 0]
<INFO>: entry .. [mode 016f0001 ino 00000001 nlink 1 size 0]
<INFO>: entry etc [mode 017f0001 ino 00000005 nlink 1 size 0]
<INFO>: entry dev<FAIL>: stat() returned -1 No such entity
<INFO>: entry bin [mode 017f0001 ino 00000003 nlink 1 size 0]
<INFO>: entry otg [mode 017f0001 ino 0000000b nlink 1 size 0]
<INFO>: entry mp3 [mode 016f0001 ino 0000000a nlink 1 size 0]
<INFO>: entry lib [mode 017f0001 ino 00000007 nlink 1 size 0]
<INFO>: entry mnt [mode 017f0001 ino 00000008 nlink 1 size 0]
<INFO>: entry var [mode 01ff0100 ino 00000015 nlink 1 size 10]
<INFO>: entry usr [mode 017f0001 ino 00000014 nlink 1 size 0]
<INFO>: entry tmp [mode 01ff0100 ino 00000011 nlink 1 size 10]
<INFO>: entry sys [mode 017f0001 ino 00000010 nlink 1 size 0]
<INFO>: entry home [mode 017f0001 ino 00000006 nlink 1 size 0]
<INFO>: entry sbin [mode 017f0001 ino 0000000e nlink 1 size 0]
<INFO>: entry proc [mode 017f0001 ino 0000000c nlink 1 size 0]
<INFO>: entry rdisk0 [mode 017f0001 ino 0000000d nlink 1 size 0]
<INFO>: entry usb_mods [mode 017f0001 ino 00000012 nlink 1 size 0]
<INFO>: entry armboot.bin [mode 017f0008 ino 00000002 nlink 1 size 108048]
<INFO>: entry scripts.sh [mode 004f0008 ino 0000000f nlink 1 size 284]
<INFO>: entry usbip_server [mode 016f0001 ino 00000013 nlink 1 size 0]
<INFO>: entry modules [mode 017f0001 ino 00000009 nlink 1 size 0]
<INFO>: create file /foo size 202
<FAIL>: open() returned -1 No space left on device
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
<FAIL>: write() returned -1 Bad file handle
Thanks & Regards
Srinivas Rao.Ch
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss
mailing list