From: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: mtd <linux-mtd@lists.infradead.org>
Subject: Re: Inode corrupted after CVS update
Date: Tue, 08 Apr 2003 10:33:24 +0200 [thread overview]
Message-ID: <3E928954.1080504@imc-berlin.de> (raw)
In-Reply-To: 1049790098.18045.91.camel@passion.cambridge.redhat.com
David Woodhouse schrieb:
> On Tue, 2003-04-08 at 08:19, Steven Scholz wrote:
>
>>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
>>
>>...
>>jffs2_get_inode_nodes(): Inode corrupted at 0x000ff370, totlen 70,
>>#ino 130, version 1, isize 0, csize 2, dsize 2
>
>
> Argh. device nodes have data in the nodes but isize is zero, triggering
> an overly-zealous sanity check. Fixed in cvs...
:o)
Thanks David!
It works now.
So how stable is the MTD/JFFS2 code anyway?
Is the CVS the only place for me to get the source?
Or are there some offical, release patches?
Thanks again,
Steven
next prev parent reply other threads:[~2003-04-08 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 7:19 Inode corrupted after CVS update Steven Scholz
2003-04-08 8:21 ` David Woodhouse
2003-04-08 8:33 ` Steven Scholz [this message]
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=3E928954.1080504@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox