public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Gunnar Ruthenberg" <Krill.Plush@gmx.net>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] JFFS2 bug with overwriting files bigger than 50% of the file system?
Date: Thu, 28 Jul 2011 13:15:00 -0000	[thread overview]
Message-ID: <20110728131533.326590@gmx.net> (raw)

Hi,

I stumbled upon a problem with JFFS2.

When overwriting a relatively large file (580 kB in a 896 kB flash region),
the file system breaks.

Plenty of errors like these ensue when trying to read the new, overwritten file
after a reboot:

BUG() at ~/ecos-2.0.40/packages/fs/jffs2/v2_0_40/src/readinode.c 381
<5>JFFS2 notice:  read_unknown: node header CRC failed at %#08x. But it must hav
e been OK earlier.
<4>Node totlen on flash (0xffffffff) != totlen from node ref (0x00000044)
<4>JFFS2 warning:  jffs2_do_read_inode_internal: no data nodes found for ino #3
<5>JFFS2 notice:  jffs2_do_read_inode_internal: but it has children so we fake s
ome modes for it
<4>JFFS2 warning:  jffs2_do_read_inode_internal: no data nodes found for ino #3
<5>JFFS2 notice:  jffs2_do_read_inode_internal: but it has children so we fake s
ome modes for it

It does not matter if the new file is identical with the old file.
Unlinking and then writing the file again causes the same result.

If this is more or less a known problem, how likely is it that small files (say,
being smaller than 50% of the file system's storage space) cause this behaviour
as well?

I noticed that the current version in the eCos source tree lags a bit behind the
code in the Linux kernel. Maybe this issue has been fixed there already and only
requires a port of the current code to eCos.

I'd be grateful for any ideas about this problem, even if it is just pointing me
to the linux-mtd mailing list.

Thanks,

Gunnar Ruthenberg.


-- 
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!		
Jetzt informieren: http://www.gmx.net/de/go/freephone

-- 
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:[~2011-07-28 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 13:15 Gunnar Ruthenberg [this message]
2011-07-28 13:36 ` Gunnar Ruthenberg
2011-08-02  6:42 ` Lambrecht Jürgen
2011-08-09 14:52   ` Gunnar Ruthenberg
2011-08-11  6:51     ` Lambrecht Jürgen

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=20110728131533.326590@gmx.net \
    --to=krill.plush@gmx.net \
    --cc=ecos-discuss@ecos.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).