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: Tue, 28 May 2013 10:44:02 +0300 [thread overview]
Message-ID: <1369727042.5446.112.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <85D877DD6EE67B4A9FCA9B9C3A4865670C3E8CBD81@SI-MBX14.de.bosch.com>
On Tue, 2013-05-28 at 09:07 +0200, Prins Anton (ST-CO/ENG1.1) wrote:
> We use a backport of UBIFS-2.6 (june 2012), and checked for important fixes in this area.
>
> Is there a way to check/find if a 'root-node' is load from flash (e.g. during recovery)?
>
> Does recovery need the 'root-node'?
I think your error was about the root inode:
"ubifs_iget: failed to read inode 1, error -2"
which is the inode of the root directory. Just like everything else, it
is stored in the index tree.
Of course the root inode is required to access the file-system. For some
reason it cannot be found. Probably if you enable all debug messages -
it may be useful.
Is this problem reproducible?
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-05-28 7:41 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 [this message]
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
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=1369727042.5446.112.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