public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Gary Thomas <gary@mlbassoc.com>,  ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: FTP runs out of JFFS2 nodes and trashes the file	system
Date: Tue, 08 Apr 2008 15:58:00 -0000	[thread overview]
Message-ID: <47FB8EFE.4030008@televic.com> (raw)
In-Reply-To: <20080408090553.GA8077@lunn.ch>

Andrew Lunn wrote:

>>But Gary says  
>>(http://ecos.sourceware.org/ml/ecos-discuss/2008-04/msg00102.html) that  
>>jffs2 automatically buffers data to fill a node, and I read yesterday  
>>something about that on infradead.org ???
>>    
>>
>
>I don't think that is correct for eCos. On Linux the VFS maybe
>blocking together writes, but for eCos there is no VFS. Writes go
>directly to the filesystem. Enabling debugging may prove this.
>
>         Andrew
>
>  
>
Here are my debug results:

- When looking to the jffs2 debug output, I see there are nodes with a 
huge number of versions: 326, 628... . Each time of size 0x100 or 256B.
- I have problems with printf... tomorrow hopefully more...

Kind regards,
Jürgen

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2008-04-08 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47FA32AC.4070705@televic.com>
2008-04-07 23:22 ` Jürgen Lambrecht
2008-04-08  6:48   ` Andrew Lunn
2008-04-08  8:41     ` Jürgen Lambrecht
2008-04-08 10:32       ` Andrew Lunn
2008-04-08 15:58         ` Jürgen Lambrecht [this message]
2008-04-09 11:42         ` Jürgen Lambrecht

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=47FB8EFE.4030008@televic.com \
    --to=j.lambrecht@televic.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.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).