All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: mtd <linux-mtd@lists.infradead.org>
Subject: Inode corrupted after CVS update
Date: Tue, 08 Apr 2003 09:19:31 +0200	[thread overview]
Message-ID: <3E927803.9060205@imc-berlin.de> (raw)

Hi there,

I pulled the CVS yesterday, patched my linuxppc-2.4.20, build and 
flashed my image.

I am using JFFS2 as root fs. While booting I get loads of

...
VFS: Mounted root (jffs2 filesystem).
Freeing unused kernel memory: 56k init
jffs2_get_inode_nodes(): Inode corrupted at 0x000ff370, totlen 70, 
#ino  130, version 1, isize 0, csize 2, dsize 2
jffs2_do_read_inode(): No data nodes found for ino #130
Warning: unable to open an initial console.
jffs2_get_inode_nodes(): Inode corrupted at 0x000ff458, totlen 70, 
#ino  132, version 1, isize 0, csize 2, dsize 2
jffs2_do_read_inode(): No data nodes found for ino #132
Returned error for crccheck of ino #132. Expect badness...
jffs2_get_inode_nodes(): Inode corrupted at 0x000ff6e0, totlen 70, 
#ino  137, version 1, isize 0, csize 2, dsize 2
jffs2_do_read_inode(): No data nodes found for ino #137
Returned error for crccheck of ino #137. Expect badness...
jffs2_get_inode_nodes(): Inode corrupted at 0x000ff758, totlen 70, 
#ino  138, version 1, isize 0, csize 2, dsize 2
jffs2_do_read_inode(): No data nodes found for ino #138
...

Any idea?

Thanks,

Steven

             reply	other threads:[~2003-04-08  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08  7:19 Steven Scholz [this message]
2003-04-08  8:21 ` Inode corrupted after CVS update David Woodhouse
2003-04-08  8:33   ` Steven Scholz
2003-04-08  8:43     ` David Woodhouse
2003-04-08  8:47       ` Steven Scholz
2003-04-08  9:08         ` David Woodhouse

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=3E927803.9060205@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.