From: Srinivas rao <ch_srinivas321@yahoo.co.in>
To: ecos <ecos-discuss@sourceware.org>
Subject: [ECOS] jffs2_1 test case error
Date: Thu, 26 Oct 2006 10:33:00 -0000 [thread overview]
Message-ID: <20061026103341.32360.qmail@web7901.mail.in.yahoo.com> (raw)
Hi All,
Iam running jffs2 test cases on my board. After
reading the directories getting error like below.
Pls give me the solution.
<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
00000004 nlink 1 size 0]
<INFO>: entry dev<FAIL>: stat() returned -1
No such entity
<INFO>: entry bin [mode 017f0001 ino
00000002 nlink 1 size 0]
<INFO>: entry lib [mode 017f0001 ino
00000005 nlink 1 size 0]
<INFO>: entry mnt [mode 017f0001 ino
00000006 nlink 1 size 0]
<INFO>: entry var [mode 017f0001 ino
000000f6 nlink 1 size 0]
<INFO>: entry tmp [mode 017f0001 ino
000000fb nlink 1 size 0]
<INFO>: entry sbin [mode 017f0001 ino
00000007 nlink 1 size 0]
<INFO>: create file /foo size 202
<5>Write of 68 bytes at 0x003e3144 failed. returned
-5, retlen 68
<5>Write of 68 bytes at 0x003e3188 failed. returned
-5, retlen 68
<FAIL>: open() returned -1 I/O error
<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
<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
<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
<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
__________________________________________________________
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
next reply other threads:[~2006-10-26 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 10:33 Srinivas rao [this message]
2006-10-26 11:34 ` Andrew Lunn
2006-10-26 12:03 ` [ECOS] Two things about cyg_types Stefan Sommerfeld
2006-10-26 13:49 ` Andrew Lunn
2006-10-26 12:56 [ECOS] jffs2_1 test case error Chris Zimman
2008-03-26 15:38 ` Jürgen Lambrecht
2008-03-26 15:51 ` Chris Zimman
2008-03-27 9:04 ` Jürgen Lambrecht
2008-03-27 9:58 ` Chris Zimman
2008-03-28 15:24 ` Jürgen Lambrecht
2008-03-29 8:35 ` Chris Zimman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061026103341.32360.qmail@web7901.mail.in.yahoo.com \
--to=ch_srinivas321@yahoo.co.in \
--cc=ecos-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).