From: "Chris Zimman" <czimman@bloomberg.com>
To: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
Cc: <ecos-discuss@sourceware.org>, "Daniel Morris" <danielm@eCosCentric.com>
Subject: RE: [ECOS] FW: Mount JFFS2 root file system issue
Date: Thu, 27 Mar 2008 12:14:00 -0000 [thread overview]
Message-ID: <F31C1582037F5041B0CD525FD870AE6A77424E@ny2545.corp.bloomberg.com> (raw)
In-Reply-To: <47EB631B.8000301@televic.com>
> We would be interested in eCosCentric's JFFS2 if - in order of
> importance
> - it would need less RAM per file
> - it would have less "strange" problems
> * if I drive JFFS2 to its limits (put it full, use very big files,
> put
> many small files in 1 directory) it can get corrupted
> * our simple FTP server corrupts JFFS2 if you put over 180 files with
> a FTP client on PC
> * the more you use JFFS2 (add and remove files), the more it trashes
> itself, so the more delay all actions have
> - it would be faster in opening files (especially in a directory with
> over 1000 files)
>
> Therefore, I want to repeat the warning from Thomas Köller: "Do not use
> large JFFS2 file systems if RAM is a scarce resource!"
> (http://sourceware.org/ml/ecos-discuss/2003-10/msg00247.html).
> And that is just what we have done..
Hi Jürgen,
I think you need to discuss these things with eCosCentric. I don't work for
them, I just recommend them because I know they provide very good service.
As I said before, they provide a supported version of JFFS2 for eCos. I
don't have the time right now to go and fix up the one in the public
repository.
--Chris
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2008-03-27 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 4:02 Lin, Bin (Bin)
2008-01-11 12:40 ` Gary Thomas
2008-01-11 15:35 ` Lin, Bin (Bin)
2008-01-11 15:40 ` Gary Thomas
2008-03-26 16:06 ` Jürgen Lambrecht
2008-03-26 17:44 ` Chris Zimman
2008-03-27 9:57 ` Jürgen Lambrecht
2008-03-27 12:14 ` Chris Zimman [this message]
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=F31C1582037F5041B0CD525FD870AE6A77424E@ny2545.corp.bloomberg.com \
--to=czimman@bloomberg.com \
--cc=J.Lambrecht@televic.com \
--cc=danielm@eCosCentric.com \
--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).