public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: <pan.kierownik@gazeta.pl>
To: linux-mtd@lists.infradead.org
Subject: [JFFS2] check_node_data: MTD point returned len too short warnings
Date: Fri, 30 Mar 2007 13:13:37 +0200 (CEST)	[thread overview]
Message-ID: <9452915.11171175253217414.JavaMail.webadm@ew6> (raw)

Hi all,

I'm currently trying to use jffs2 on mtd device on our ARM926EJ-S
development board. We have here Intel Sibley 512Mb flash memory,
uClinux with kernel 2.6.19-uc1 and following problem:

    /> unlock /dev/mtd3
    /> eraseall /dev/mtd3
    Erasing 256 Kibyte @ fc0000 -- 98 % complete.
    /> mount -t jffs2 -o noatime /dev/mtdblock3 /mnt
    /> cp -r /bin /mnt
    /> sync
    /> umount /mnt
    /> mount -t jffs2 -o noatime /dev/mtdblock3 /mnt
    <4>JFFS2 warning: (176) check_node_data: MTD point returned len
too short: 1573 instead of 2577.
    <4>JFFS2 warning: (176) check_node_data: MTD point returned len
too short: 1998 instead of 2394.
    ... and so on - message repeated hundreds of time

After mounting file system I can run programs from that partition
without any problem.

I've tried to create jffs2 using mkfs.jffs2 (v1.43) on host:
    mkfs.jffs2 -p -rromfs -e262144 -offs.bin -c1024 -s1024
and then write directly to the flash where mtd3 partition is
located. The same warnings are displayed.

I tried to place jffs2 root file system in flash and start kernel
with following parameters:
    root=/dev/mtdblock3 rw rootfstype=jffs2 noinitrd init=/bin/init
console=ttyJ0 rootflags=noatime

When it comes to mount rootfs, the same check_node_data warnings
occurs and kernel panics. But for now, I just would like to get rid
of these warnings.

Best regards,
Krzysztof

                 reply	other threads:[~2007-03-30 11:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9452915.11171175253217414.JavaMail.webadm@ew6 \
    --to=pan.kierownik@gazeta.pl \
    --cc=linux-mtd@lists.infradead.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