From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Prins Anton (ST-CO/ENG1.1)" <Anton.Prins@nl.bosch.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Jan Kara <jack@suse.cz>, Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: UBIFS failure & stable page writes
Date: Wed, 29 May 2013 09:49:18 +0300 [thread overview]
Message-ID: <1369810158.5446.208.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <85D877DD6EE67B4A9FCA9B9C3A4865670C3E91DC9C@SI-MBX14.de.bosch.com>
On Tue, 2013-05-28 at 13:13 +0200, Prins Anton (ST-CO/ENG1.1) wrote:
> Will add the CFLAG -DDEBUG and debug further!
> (I hope at this kernel-recovery stage there are not debug messages of multiple partitions because there are more UBIFS partitions.)
>
> Doing this I saw some suspicious messages like:
> UBIFS DBG rcvry: deleting orphaned inode 0
> ...
> UBIFS DBG rcvry: deleting orphaned inode 1
> ...
These are very strange messages. Inode 0 should not exist. Inode 1
should be impossible to ever delete. Smells like some kind of memory
corruption. Can you share your image? Or at least the orphan areas of
the image? We do not have much time, but would probably take a look.
Would also be useful to have the fs/ubifs/* and drivers/mtd/ubi/* of
yours.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-05-29 6:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85D877DD6EE67B4A9FCA9B9C3A4865670C3E8CB9B7@SI-MBX14.de.bosch.com>
[not found] ` <4BE1E71893EF1E4F9E9DD99FB4EBF0032C02EA2D44@SI-MBX02.de.bosch.com>
[not found] ` <85D877DD6EE67B4A9FCA9B9C3A4865670C3E8CBA85@SI-MBX14.de.bosch.com>
2013-05-27 12:18 ` UBIFS failure & stable page writes Jan Kara
2013-05-27 13:13 ` Prins Anton (ST-CO/ENG1.1)
2013-05-28 2:57 ` Artem Bityutskiy
2013-05-28 7:07 ` Prins Anton (ST-CO/ENG1.1)
2013-05-28 7:44 ` Artem Bityutskiy
2013-05-28 8:18 ` Prins Anton (ST-CO/ENG1.1)
2013-05-28 9:11 ` Artem Bityutskiy
2013-05-28 11:13 ` Prins Anton (ST-CO/ENG1.1)
2013-05-29 6:49 ` Artem Bityutskiy [this message]
2013-05-29 11:06 ` Prins Anton (ST-CO/ENG1.1)
2013-05-31 9:51 ` Prins Anton (ST-CO/ENG1.1)
2013-06-03 6:01 ` Artem Bityutskiy
2013-06-11 12:16 ` Prins Anton (ST-CO/ENG1.1)
2013-06-12 7:58 ` Adrian Hunter
2013-06-12 8:28 ` Prins Anton (ST-CO/ENG1.1)
2013-06-12 11:40 ` Adrian Hunter
2013-06-12 11:13 ` Prins Anton (ST-CO/ENG1.1)
2013-06-12 12:00 ` Adrian Hunter
2013-06-12 11:57 ` Prins Anton (ST-CO/ENG1.1)
2013-06-12 13:09 ` Adrian Hunter
2013-06-12 13:57 ` Prins Anton (ST-CO/ENG1.1)
2013-06-13 10:54 ` Mats Kärrman
2013-06-13 13:31 ` Prins Anton (ST-CO/ENG1.1)
2013-06-13 13:41 ` Adrian Hunter
2013-06-13 14:02 ` Prins Anton (ST-CO/ENG1.1)
2013-06-15 22:25 ` Mats Kärrman
2013-06-13 19:24 ` Prins Anton (ST-CO/ENG1.1)
2013-06-15 22:45 ` Mats Kärrman
2013-06-17 11:20 ` Prins Anton (ST-CO/ENG1.1)
2013-06-18 6:31 ` Prins Anton (ST-CO/ENG1.1)
2013-06-18 7:01 ` Adrian Hunter
2013-06-18 7:17 ` Prins Anton (ST-CO/ENG1.1)
2013-06-25 8:21 ` Prins Anton (ST-CO/ENG1.1)
2013-06-28 9:05 ` Mats Kärrman
2013-06-28 9:27 ` Prins Anton (ST-CO/ENG1.1)
2013-07-25 13:18 ` Prins Anton (ST-CO/ENG1.1)
2013-06-12 7:12 ` Prins Anton (ST-CO/ENG1.1)
2013-05-28 13:00 ` Prins Anton (ST-CO/ENG1.1)
2013-06-13 7:41 ` Adrian Hunter
2013-05-28 8:15 ` Prins Anton (ST-CO/ENG1.1)
2013-05-28 9:09 ` Artem Bityutskiy
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=1369810158.5446.208.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=Anton.Prins@nl.bosch.com \
--cc=adrian.hunter@intel.com \
--cc=jack@suse.cz \
--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