From: Artem Bityutskiy <dedekind1@gmail.com>
To: Koen Beel <koen.beel.barco@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>,
linux-mtd@lists.infradead.org, adrian.hunter@intel.com
Subject: Re: ubifs_iget: failed to read inode 1
Date: Fri, 29 Jun 2012 17:13:34 +0300 [thread overview]
Message-ID: <1340979214.3070.218.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAHMSPgOUuq8HKR+Q3ay5jr4-cYQYcB5129p4XcHYi4z2ydoH6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On Fri, 2012-06-29 at 10:48 +0200, Koen Beel wrote:
> Hi all,
>
> We are using UBIFS on nand flash and experienced the following issue.
> During attach of the ubi device we get the message 'recovery needed'
> and 'recovery complete'. Finally the ubi_attach fails with the error
> "UBIFS error (pid 229): ubifs_iget: failed to read inode 1, error -2".
>
> We are using and Freescale i.MX28 soc and using Micron NAND (see below).
> We are using kernel version 3.1.0.
> We have tested with latest mainline kernel but have not been able to
> trigger this issue.
> However, once the issue in the the flash, it can be reproduced at every boot.
>
> Looking at the ubifs code, the error message traces back to:
> ubifs_iget: ubifs_tnc_lookup fails, goto out_ino, free mem and print error.
> ubifs_tnc_lookup
> ubifs_tnc_locate: returns -ENOENT (-2)
> ubifs_lookup_level0: the lookup fails
Something related to how you flash your image or to your driver. Run mtd
tests to start with. Try on nandsim. Try to mount empty flash, write
data, unmount, mount again.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-06-29 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 8:48 ubifs_iget: failed to read inode 1 Koen Beel
2012-06-29 9:15 ` Huang Shijie
2012-06-29 14:13 ` Artem Bityutskiy [this message]
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=1340979214.3070.218.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=b32955@freescale.com \
--cc=koen.beel.barco@gmail.com \
--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