public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Igor Marnat <marny@rambler.ru>
To: linux-mtd-bounces@lists.infradead.org,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: jffs2_gcd_mtd0 invoked oom-killer
Date: Wed, 21 Mar 2007 00:02:39 +0300	[thread overview]
Message-ID: <1014706625.20070321000239@rambler.ru> (raw)
In-Reply-To: <1174323006.13341.504.camel@localhost.localdomain>

Hello Thomas,

TG>  Invalid Inode      node at 0x000253ec, totlen 0x00000130, #ino   1807, version 106033, isize 428154883, csize     4597, dsize     4597, offset 37875712
TG>  Invalid Inode      node at 0x00025a14, totlen 0x00000046, #ino   8620, version 470658, isize 1019416371, csize     3596, dsize     3596, offset  5997846
TG>  Invalid Inode      node at 0x00025e20, totlen 0x00000091, #ino   8620, version 470663, isize  5997941, csize 3438493594, dsize 4294927703, offset  5997864

TG> Interrestingly enough are the node CRCs of some of the nodes intact, so
TG> the corruption must have happened before writing to flash.

TG> Does the patch below help ?

Unfortunately no, it still crashes in the same way.

Should I attach any debug output or something?

-- 
Best regards,
Igor Marnat
mailto:marny@rambler.ru

  reply	other threads:[~2007-03-20 21:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 12:28 jffs2_gcd_mtd0 invoked oom-killer Igor Marnat
2007-03-12 13:10 ` Artem Bityutskiy
2007-03-19  5:45   ` Igor Marnat
2007-03-19  7:19     ` Thomas Gleixner
2007-03-19 11:48       ` Igor Marnat
2007-03-19 16:50         ` Thomas Gleixner
2007-03-20 21:02           ` Igor Marnat [this message]
2007-03-21  8:14           ` Igor Marnat
2007-03-21  9:17             ` Thomas Gleixner
2007-03-21 11:40               ` Igor Marnat
2007-03-28  5:15               ` Igor Marnat

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=1014706625.20070321000239@rambler.ru \
    --to=marny@rambler.ru \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd-bounces@lists.infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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