From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19754 invoked by alias); 7 Oct 2003 13:04:09 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 19736 invoked from network); 7 Oct 2003 13:04:08 -0000 Received: from unknown (HELO londo.lunn.ch) (80.238.139.98) by sources.redhat.com with SMTP; 7 Oct 2003 13:04:08 -0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1A6rVS-00049Z-00; Tue, 07 Oct 2003 15:04:02 +0200 Date: Tue, 07 Oct 2003 13:04:00 -0000 To: oyvind.harboe@zylin.com Cc: ecos-discuss@sources.redhat.com Message-ID: <20031007130402.GB15932@lunn.ch> Mail-Followup-To: oyvind.harboe@zylin.com, ecos-discuss@sources.redhat.com References: <1065524219.5485.43.camel@famine> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1065524219.5485.43.camel@famine> User-Agent: Mutt/1.5.4i From: Andrew Lunn Subject: Re: [ECOS] Stress testing JFFS2 X-SW-Source: 2003-10/txt/msg00096.txt.bz2 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