The Linux Memory Technology Driver subsystem

Koen Beel | 29 Jun 2012 10:48

ubifs_iget: failed to read inode 1

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

Anybody an idea where to look for?

Thanks,
Koen

Uncompressing Linux... done, booting the kernel.
[    0.000000] Linux version 3.1.0 (jenkins <at> oxygen.barco.com) (gcc
version 4.5.3 (Buildroot 2011.11-svn3549-dirty) ) #3 Wed Jun 27
11:58:26 CEST 2012
[    0.000000] Kernel command line: panic=3 oops=panic console=ttyAMA0,115200
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)

(Continue reading)

headers

Huang Shijie | 29 Jun 2012 11:15

Re: ubifs_iget: failed to read inode 1

Hi:
Please try this patch:

http://lists.infradead.org/pipermail/linux-mtd/2012-June/042461.html

Huang Shijie
> 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
>
> Anybody an idea where to look for?
>
> Thanks,
> Koen
>

(Continue reading)

headers

Artem Bityutskiy | 29 Jun 2012 16:13

Re: ubifs_iget: failed to read inode 1

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

______________________________________________________

(Continue reading)