UBIFS always readonly - ubifs_iget: failed to read inode 11414, error -22

[Artem Bityutskiy]

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

Hmm, s similar report as another I got recently [1]. Similar symptoms, a
bit different kind of garbage in znode. I guess my answers to this are
similar:

1. Never saw before
2. Node dump is absent, try ingore_loglevel. Would make sens to dump the
node, may be we could have some clue from the dump?
3. Kernel is ancient.
4. May be a memory corruption. But may be a bug in UBIFS.

Probably if you could somehow make this reproducible, we could think how
find out what triggers this.

1.
http://lists.infradead.org/pipermail/linux-mtd/2012-November/044970.html

-- 
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20121130/3ce5b083/attachment.sig>