From: Andrew Lunn <andrew@lunn.ch>
To: oyvind.harboe@zylin.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Stress testing JFFS2
Date: Tue, 07 Oct 2003 13:04:00 -0000 [thread overview]
Message-ID: <20031007130402.GB15932@lunn.ch> (raw)
In-Reply-To: <1065524219.5485.43.camel@famine>
On Tue, Oct 07, 2003 at 12:57:00PM +0200, ?yvind Harboe wrote:
> Today stress testing JFFS2 came up on the agenda, and I wrote a small
> piece that demonstrates a problem with JFFS2 running out of space
> when it shouldn't, leaving a corrupt JFFS2 image and continuously
> allocating more ram.
>
> The test consists of writing lots of files that overwrite existing
> files. The total number of files is never >16.
>
> /config is a JFFS2 fs. 6*0x10000bytes.
>
> Should I expect this sort of thing to never fail and to
> reach a plateau of memory usage?
Please could you give us a complete test case. Something we can run
ourselves. Create a new bugzilla bug on bugs.ecos.sourceware.org and
include the source code and the ecos configuration you are using.
That will make it much easier for us to see whats happening.
> Output:
>
>
> Created file 0 153284 bytes ram free
> Created file 100 149132 bytes ram free
> Created file 200 146732 bytes ram free
> Created file 300 144332 bytes ram free
> Created file 400 141932 bytes ram free
> Created file 500 139532 bytes ram free
> Created file 600 137132 bytes ram free
> Created file 700 134732 bytes ram free
> Created file 800 132332 bytes ram free
> Failed
What is failing? open, write, close?
There could actually to two things going one. A plain memory leak and
some other jffs2 problem. I would first investige the call that is
failing. Find out exactly where it fails and hence why.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-10-07 13:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 10:57 Øyvind Harboe
2003-10-07 12:31 ` David Vrabel
2003-10-07 13:04 ` Andrew Lunn [this message]
2003-10-07 13:16 ` Øyvind Harboe
2003-10-07 13:43 ` Andrew Lunn
2003-10-07 16:42 ` Thomas Koeller
2003-10-07 17:57 ` Andrew Lunn
2003-10-08 8:34 ` Thomas Koeller
2003-10-07 13:36 ` Eric Donnat
2003-10-07 16:43 Øyvind Harboe
2003-10-08 7:37 Øyvind Harboe
2003-10-08 9:07 ` Jani Monoses
2003-10-15 10:07 ` Thomas Koeller
2003-10-15 10:52 ` David Woodhouse
2003-10-15 11:26 ` Thomas Koeller
2003-10-16 10:25 ` David Woodhouse
2003-10-15 11:53 Dinesh Kumar
2003-10-15 12:54 ` Thomas Koeller
2003-10-15 18:33 Doug Fraser
2003-10-16 7:23 Øyvind Harboe
2003-10-16 7:32 ` Andrew Lunn
2003-10-16 7:35 ` Øyvind Harboe
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=20031007130402.GB15932@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=oyvind.harboe@zylin.com \
/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).