From: Artem Bityutskiy <dedekind1@gmail.com>
To: Thomas Bechtold <thomasbechtold@jpberlin.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS always readonly - ubifs_iget: failed to read inode 11414, error -22
Date: Thu, 22 Nov 2012 11:08:43 +0200 [thread overview]
Message-ID: <1353575323.2701.25.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <50ADDF4A.90506@jpberlin.de>
[-- Attachment #1: Type: text/plain, Size: 2606 bytes --]
On Thu, 2012-11-22 at 09:16 +0100, Thomas Bechtold wrote:
> Hi,
>
> I use UBIFS with upstream kernel 3.2.32 on an ARMv5 (Stamp9G20) and NAND
> Flash. When the device starts, the root-fs is mounted readonly. I can
> not remount the FS. The FAQ [1] told me that I can ask here for help.
> The device is remote and only accessable over ssh. It's expensive to go
> there so it would be nice if something could be done to repair the FS
> remotely.
>
> The output from dmesg is:
>
> #################### BEGIN #########################
> # dmesg |grep -i ubi
> Kernel command line: console=ttyS0,115200 mem=128M
> mtdparts=atmel_nand:128k(bootstrap)ro,256k(uboot),128k(env1),128k(env2),2M(linux),-(root)rw
> ubi.mtd=5 root=ubi0_0 rootfstype=ubifs boardtype=revC
> UBI: attaching mtd5 to ubi0
> UBI: physical eraseblock size: 131072 bytes (128 KiB)
> UBI: logical eraseblock size: 129024 bytes
> UBI: smallest flash I/O unit: 2048
> UBI: sub-page size: 512
> UBI: VID header offset: 512 (aligned 512)
> UBI: data offset: 2048
> UBI: max. sequence number: 5115
> UBI: attached mtd5 to ubi0
> UBI: MTD device name: "root"
> UBI: MTD device size: 509 MiB
> UBI: number of good PEBs: 4064
> UBI: number of bad PEBs: 11
> UBI: number of corrupted PEBs: 0
> UBI: max. allowed volumes: 128
> UBI: wear-leveling threshold: 4096
> UBI: number of internal volumes: 1
> UBI: number of user volumes: 1
> UBI: available PEBs: 119
> UBI: total number of reserved PEBs: 3945
> UBI: number of PEBs reserved for bad PEB handling: 40
> UBI: max/mean erase counter: 39/1
> UBI: image sequence number: -393607928
> UBI: background thread "ubi_bgt0d" started, PID 248
> TCP cubic registered
> UBIFS: recovery needed
> UBIFS: recovery completed
> UBIFS: mounted UBI device 0, volume 0, name "m40rootfs"
> UBIFS: file system size: 501387264 bytes (489636 KiB, 478 MiB, 3886 LEBs)
> UBIFS: journal size: 25159680 bytes (24570 KiB, 23 MiB, 195 LEBs)
> UBIFS: media format: w4/r0 (latest is w4/r0)
> UBIFS: default compressor: lzo
> UBIFS: reserved for root: 4952683 bytes (4836 KiB)
> VFS: Mounted root (ubifs filesystem) on device 0:10.
> UBIFS error (pid 1): read_znode: bad indexing node at LEB 3174:70736,
> error 6
> UBIFS error (pid 1): ubifs_iget: failed to read inode 11414, error -22
> UBIFS error (pid 1): ubifs_lookup: dead directory entry
> 'custom-loco.conf', error -22
Is this reproducible?
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-22 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 8:16 UBIFS always readonly - ubifs_iget: failed to read inode 11414, error -22 Thomas Bechtold
2012-11-22 9:08 ` Artem Bityutskiy [this message]
2012-11-22 9:25 ` Thomas Bechtold
2012-11-30 12:11 ` 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=1353575323.2701.25.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=thomasbechtold@jpberlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.