From: Timo Ketola <Timo.Ketola@exertus.fi>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Power cut leads to "corrupt empty space"
Date: Thu, 27 Feb 2020 13:04:25 +0000 [thread overview]
Message-ID: <ee9d424c-8b89-c8f6-7b3b-1ab09371e04c@exertus.fi> (raw)
Hi,
We have a few i.MX6D devices which have corrupted their UBIFS filesystem
on power cut and refuse to mount them any more.
The log says:
> [ 10.382580] UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 158
> [ 10.408838] UBIFS (ubi1:0): recovery needed
> [ 10.802070] UBIFS error (ubi1:0 pid 157): ubifs_scan: corrupt empty space at
> LEB 99:114688
> [ 10.809054] UBIFS error (ubi1:0 pid 157): ubifs_scanned_corruption: corruptio
> n at LEB 99:114688
> [ 10.816471] UBIFS error (ubi1:0 pid 157): ubifs_scanned_corruption: first 819
> 2 bytes from LEB 99:114688
> [ 10.824585] 00000000: 06101831 713b7e1b 002e0640 00000000 000000a0 00000200 0
> 0000554 00000000 1....~;q@...............T.......
> [ 10.824601] 00000020: 00000000 00000000 0001585b 00000000 0008c48d 00000000 5
> d512897 00000000 ........[X...............(Q]....
...
> [ 10.827751] UBIFS error (ubi1:0 pid 157): ubifs_scan: LEB 99 scanning failed
> [ 10.834615] UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
I think I found the culprit from the mtdblock contents. Fragment from
hexdump:
> 3ca20000 55 42 49 23 01 00 00 00 00 00 00 00 00 00 00 04 |UBI#............|
> 3ca20010 00 00 08 00 00 00 10 00 0c 4d 7c ed 00 00 00 00 |.........M|.....|
> 3ca20020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca20030 00 00 00 00 00 00 00 00 00 00 00 00 cb 5d 1f 01 |.............]..|
> 3ca20040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> *
> 3ca20800 55 42 49 21 01 01 00 00 00 00 00 00 00 00 00 63 |UBI!...........c|
> 3ca20810 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca20820 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8d 07 |................|
> 3ca20830 00 00 00 00 00 00 00 00 00 00 00 00 91 2b 87 87 |.............+..|
> 3ca20840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> *
> 3ca21000 31 18 10 06 30 3c 6d 96 cd 05 2e 00 00 00 00 00 |1...0<m.........|
> 3ca21010 a0 00 00 00 00 02 00 00 54 05 00 00 00 00 00 00 |........T.......|
...
> 3ca3b8c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> *
> 3ca3c000 31 18 10 06 7b 71 87 8f 3c 06 2e 00 00 00 00 00 |1...{q..<.......|
> 3ca3c010 a0 00 00 00 00 02 00 00 54 05 00 00 00 00 00 00 |........T.......|
> 3ca3c020 00 00 00 00 00 00 00 00 5b 58 01 00 00 00 00 00 |........[X......|
> 3ca3c030 79 c3 08 00 00 00 00 00 97 28 51 5d 00 00 00 00 |y........(Q]....|
> 3ca3c040 19 58 6d 38 00 00 00 00 19 58 6d 38 00 00 00 00 |.Xm8.....Xm8....|
> 3ca3c050 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 |................|
> 3ca3c060 eb 03 00 00 eb 03 00 00 a4 81 00 00 01 00 00 00 |................|
> 3ca3c070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca3c080 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca3c090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca3c0a0 31 18 10 06 84 13 e1 a0 00 00 00 00 00 00 00 00 |1...............|
> 3ca3c0b0 1c 00 00 00 05 00 00 00 44 07 00 00 00 00 00 00 |........D.......|
> 3ca3c0c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> *
> 3ca3c800 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
> *
> 3ca3d000 31 18 10 06 1b 7e 3b 71 40 06 2e 00 00 00 00 00 |1....~;q@.......|
> 3ca3d010 a0 00 00 00 00 02 00 00 54 05 00 00 00 00 00 00 |........T.......|
> 3ca3d020 00 00 00 00 00 00 00 00 5b 58 01 00 00 00 00 00 |........[X......|
> 3ca3d030 8d c4 08 00 00 00 00 00 97 28 51 5d 00 00 00 00 |.........(Q]....|
> 3ca3d040 19 58 6d 38 00 00 00 00 19 58 6d 38 00 00 00 00 |.Xm8.....Xm8....|
> 3ca3d050 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 |................|
> 3ca3d060 eb 03 00 00 eb 03 00 00 a4 81 00 00 01 00 00 00 |................|
> 3ca3d070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca3d080 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca3d090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca3d0a0 31 18 10 06 84 13 e1 a0 00 00 00 00 00 00 00 00 |1...............|
> 3ca3d0b0 1c 00 00 00 05 00 00 00 44 07 00 00 00 00 00 00 |........D.......|
> 3ca3d0c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> *
> 3ca3d800 31 18 10 06 c1 6b e6 57 42 06 2e 00 00 00 00 00 |1....k.WB.......|
> 3ca3d810 a0 00 00 00 00 02 00 00 54 05 00 00 00 00 00 00 |........T.......|
> 3ca3d820 00 00 00 00 00 00 00 00 5b 58 01 00 00 00 00 00 |........[X......|
> 3ca3d830 0d c5 08 00 00 00 00 00 97 28 51 5d 00 00 00 00 |.........(Q]....|
> 3ca3d840 19 58 6d 38 00 00 00 00 19 58 6d 38 00 00 00 00 |.Xm8.....Xm8....|
> 3ca3d850 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 |................|
> 3ca3d860 eb 03 00 00 eb 03 00 00 a4 81 00 00 01 00 00 00 |................|
> 3ca3d870 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca3d880 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca3d890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 3ca3d8a0 31 18 10 06 84 13 e1 a0 00 00 00 00 00 00 00 00 |1...............|
> 3ca3d8b0 1c 00 00 00 05 00 00 00 44 07 00 00 00 00 00 00 |........D.......|
> 3ca3d8c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> *
> 3ca3e000 31 18 10 06 0b 75 3d 9e 44 06 2e 00 00 00 00 00 |1....u=.D.......|
IIUC, ubifs_scan finds empty space at 3ca3c800, stops scanning and
checks the rest of the LEB for being empty but finds something else at
3ca3d000. Then recovery aborts and mounting fails.
Do I understand correctly that empty space should always be continuous
at the end of the LEB?
How could this kind of corruption happen?
Is there any way to recover from this?
Storage is NAND with 0x20000 erase block size and the kernel is 4.9.88.
--
Timo
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-02-27 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 13:04 Timo Ketola [this message]
2020-02-27 13:08 ` Power cut leads to "corrupt empty space" Fabio Estevam
2020-02-27 13:42 ` Timo Ketola
2020-02-27 15:16 ` Fabio Estevam
2020-02-29 12:46 ` Timo Ketola
2020-02-29 13:13 ` Fabio Estevam
2020-02-29 14:20 ` Timo Ketola
2020-03-01 21:28 ` Richard Weinberger
2020-03-02 12:57 ` Timo Ketola
2020-03-02 21:02 ` Richard Weinberger
2020-03-03 6:27 ` Timo Ketola
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=ee9d424c-8b89-c8f6-7b3b-1ab09371e04c@exertus.fi \
--to=timo.ketola@exertus.fi \
--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;
as well as URLs for NNTP newsgroup(s).