From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Stress testing JFFS2
Date: Tue, 07 Oct 2003 10:57:00 -0000 [thread overview]
Message-ID: <1065524219.5485.43.camel@famine> (raw)
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?
20-30k ram seems excessive for 16 files.
char *args="dummy";
for (int i=0; i<10000; i++)
{
char name[5];
for (int j=0; j<(sizeof(name)-1); j++)
{
name[j]=rand()%2+'a';
};
name[4]=0;
char nameBuffer[100];
sprintf(nameBuffer, "/config/%s", name);
int fd;
fd = open( nameBuffer, O_WRONLY|O_CREAT|O_TRUNC );
if (fd<0)
{
diag_printf("Failed\r\n");
break;
}
int len=strlen(args);
ssize_t actual;
actual=write(fd, args, len);
if (actual<0)
{
diag_printf("Failed\r\n");
break;
}
int err;
err=close(fd);
if (err<0)
{
diag_printf("Failed\r\n");
break;
}
struct mallinfo info;
info = mallinfo();
if ((i%100)==0)
{
diag_printf("Created file %d %d bytes ram free\r\n", i,
info.maxfree);
}
}
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
--
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 reply other threads:[~2003-10-07 10:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 10:57 Øyvind Harboe [this message]
2003-10-07 12:31 ` David Vrabel
2003-10-07 13:04 ` Andrew Lunn
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=1065524219.5485.43.camel@famine \
--to=oyvind.harboe@zylin.com \
--cc=ecos-discuss@sources.redhat.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).