UBIFS failure & stable page writes
Prins Anton (ST-CO/ENG1.1)
Anton.Prins at nl.bosch.com
Wed Jun 12 04:28:22 EDT 2013
Thanks for the analysis,
I did do exactly the same before, but the plaster didn’t help. Here the log result; it still fails on the root node :(
Actually the root cause happens on a previous run/life-time; The question is how to get log information on this moment.
(More because we don't know how to reproduce except have many systems on for longer time)
<7>UBIFS DBG (pid 767): ubifs_bg_thread: background thread "ubifs_bgt1_1" started, PID 767
<5>UBIFS: recovery needed
<3>LEB 9
<3>deleting orphaned inode 821482
<3>last orph node for commit 1376 at 9:0
<3>deleting orphaned inode 977567
<3>last orph node for commit 1395 at 9:4096
<3>deleting orphaned inode 985932
<3>last orph node for commit 1396 at 9:8192
<3>prevent deleting orphaned inode 0
<5>UBIFS: recovery completed
<5>UBIFS: mounted UBI device 1, volume 1, name "datafs"
<5>UBIFS: file system size: 640475136 bytes (625464 KiB, 610 MiB, 1241 LEBs)
<5>UBIFS: journal size: 10452992 bytes (10208 KiB, 9 MiB, 21 LEBs)
<5>UBIFS: media format: w4/r0 (latest is w4/r0)
<5>UBIFS: default compressor: lzo
<5>UBIFS: reserved for root: 0 bytes (0 KiB)
<7>UBIFS DBG (pid 1): mount_ubifs: compiled on: May 31 2013 at 14:58:10
<7>UBIFS DBG (pid 1): mount_ubifs: min. I/O unit size: 4096 bytes
<7>UBIFS DBG (pid 1): mount_ubifs: max. write size: 4096 bytes
<7>UBIFS DBG (pid 1): mount_ubifs: LEB size: 516096 bytes (504 KiB)
<7>UBIFS DBG (pid 1): mount_ubifs: data journal heads: 1
<7>UBIFS DBG (pid 1): mount_ubifs: UUID: 1D1AD726-53AB-4623-8D86-B7773B5EFA83
<7>UBIFS DBG (pid 1): mount_ubifs: big_lpt 0
<7>UBIFS DBG (pid 1): mount_ubifs: log LEBs: 4 (3 - 6)
<7>UBIFS DBG (pid 1): mount_ubifs: LPT area LEBs: 2 (7 - 8)
<7>UBIFS DBG (pid 1): mount_ubifs: orphan area LEBs: 1 (9 - 9)
<7>UBIFS DBG (pid 1): mount_ubifs: main area LEBs: 1241 (10 - 1250)
<7>UBIFS DBG (pid 1): mount_ubifs: index LEBs: 31
<7>UBIFS DBG (pid 1): mount_ubifs: total index bytes: 702944 (686 KiB, 0 MiB)
<7>UBIFS DBG (pid 1): mount_ubifs: key hash type: 0
<7>UBIFS DBG (pid 1): mount_ubifs: tree fanout: 8
<7>UBIFS DBG (pid 1): mount_ubifs: reserved GC LEB: 166
<7>UBIFS DBG (pid 1): mount_ubifs: first main LEB: 10
<7>UBIFS DBG (pid 1): mount_ubifs: max. znode size 240
<7>UBIFS DBG (pid 1): mount_ubifs: max. index node size 192
<7>UBIFS DBG (pid 1): mount_ubifs: node sizes: data 48, inode 160, dentry 56
<7>UBIFS DBG (pid 1): mount_ubifs: node sizes: trun 56, sb 4096, master 512
<7>UBIFS DBG (pid 1): mount_ubifs: node sizes: ref 64, cmt. start 32, orph 32
<7>UBIFS DBG (pid 1): mount_ubifs: max. node sizes: data 4144, inode 4256 dentry 312, idx 188
<7>UBIFS DBG (pid 1): mount_ubifs: dead watermark: 4096
<7>UBIFS DBG (pid 1): mount_ubifs: dark watermark: 8192
<7>UBIFS DBG (pid 1): mount_ubifs: LEB overhead: 2240
<7>UBIFS DBG (pid 1): mount_ubifs: max. dark space: 10166272 (9928 KiB, 9 MiB)
<7>UBIFS DBG (pid 1): mount_ubifs: maximum bud bytes: 8388608 (8192 KiB, 8 MiB)
<7>UBIFS DBG (pid 1): mount_ubifs: BG commit bud bytes: 6815744 (6656 KiB, 6 MiB)
<7>UBIFS DBG (pid 1): mount_ubifs: current bud bytes 405504 (396 KiB, 0 MiB)
<7>UBIFS DBG (pid 1): mount_ubifs: max. seq. number: 8296008
<7>UBIFS DBG (pid 1): mount_ubifs: commit number: 1461
<3>UBIFS error (pid 1): ubifs_iget: failed to read inode 1, error -2
<7>UBIFS DBG (pid 767): ubifs_bg_thread: background thread "ubifs_bgt1_1" stops
Met vriendelijke groeten | Best Regards,
Anton Prins
-----Original Message-----
From: Adrian Hunter [mailto:adrian.hunter at intel.com]
Sent: woensdag 12 juni 2013 9:58
To: Prins Anton (ST-CO/ENG1.1)
Cc: dedekind1 at gmail.com; linux-mtd at lists.infradead.org
Subject: Re: UBIFS failure & stable page writes
This shows that the orphan area has recorded the orphaning of inode 0 (non-existent!) and inode 1 (root inode!!!).
A sticking plaster solution is to prevent orphans-processing from deleting the root inode e.g.
diff --git a/fs/ubifs/orphan.c b/fs/ubifs/orphan.c
index ba32da3..9400b5b 100644
--- a/fs/ubifs/orphan.c
+++ b/fs/ubifs/orphan.c
@@ -613,6 +613,11 @@ static int do_kill_orphans(struct ubifs_info *c, struct ubifs_scan_leb *sleb,
n = (le32_to_cpu(orph->ch.len) - UBIFS_ORPH_NODE_SZ) >> 3;
for (i = 0; i < n; i++) {
inum = le64_to_cpu(orph->inos[i]);
+ if (inum < UBIFS_FIRST_INO) {
+ ubifs_err("*not* deleting orphaned inode %lu",
+ (unsigned long)inum);
+ continue;
+ }
dbg_rcvry("deleting orphaned inode %lu",
(unsigned long)inum);
err = ubifs_tnc_remove_ino(c, inum);
On 11/06/13 15:16, Prins Anton (ST-CO/ENG1.1) wrote:
> Hi Artem,
>
> We got logging inside the recovery procedure to print the 'orphan LEB' information.
> I wonder if the LEB9 moves yes/no? So is it safe to use 'dd' with an offset of 9*LEB?
> (Difficulty is we have no file system, so this was the first option...)
>
> You see flood of message's; but I suppose the first part is the information required!
> If not I have to make some solution to go for 'dd'.
>
> Thanks in advance,
>
> Anton
>
>
>
> leb9dump-filtered.log
>
>
> UBIFS: parse sync
> UBIFS: recovery needed
> ubi_leb_read datafs 9
> 00000000: 31 18 10 06 1a c9 4a be 09 ca 5d 00 00 00 00 00 28 00 00 00 0b 00 00 00 60 05 00 00 00 00 00 80 1.....J...].....(.......`.......
> 00000020: ea 88 0c 00 00 00 00 00 31 18 10 06 74 7c 20 ed 00 00 00 00 00 00 00 00 1c 00 00 00 05 00 00 00 ........1...t| .................
> 00000040: bc 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
> 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
struct ubifs_ch {
__le32 magic; 06101831 06101831
__le32 crc; be4ac91a ed207c74
__le64 sqnum; 5dca09 0
__le32 len; 28 1c
__u8 node_type; b=orph 5=pad
__u8 group_type; 0 0
__u8 padding[2]; 0 0
} __packed;
struct ubifs_orph_node {
struct ubifs_ch ch;
__le64 cmt_no; 60 05 00 00 00 00 00 80
__le64 inos[]; 0c88ea
} __packed;
struct ubifs_pad_node {
struct ubifs_ch ch;
__le32 pad_len; 0fbc
} __packed;
<snip>
> 00001000: 31 18 10 06 33 f1 d9 f4 0c 80 6e 00 00 00 00 00 28 00 00 00 0b 00 00 00 73 05 00 00 00 00 00 80 1...3.....n.....(.......s.......
> 00001020: 9f ea 0e 00 00 00 00 00 31 18 10 06 74 7c 20 ed 00 00 00 00 00 00 00 00 1c 00 00 00 05 00 00 00 ........1...t| .................
> 00001040: bc 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
> 00001060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
__le32 len; 28
__le64 cmt_no; 73 05 00 00 00 00 00 80
__le64 inos[]; 0eea9f
<snip>
> 00002000: 31 18 10 06 c0 79 a0 c5 35 65 6f 00 00 00 00 00 28 00 00 00 0b 00 00 00 74 05 00 00 00 00 00 80 1....y..5eo.....(.......t.......
> 00002020: 4c 0b 0f 00 00 00 00 00 31 18 10 06 74 7c 20 ed 00 00 00 00 00 00 00 00 1c 00 00 00 05 00 00 00 L.......1...t| .................
> 00002040: bc 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
> 00002060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
__le32 len; 28
__le64 cmt_no; 74 05 00 00 00 00 00 80
__le64 inos[]; 0f0b4c
<snip>
> 00003000: 31 18 10 06 f8 40 ed 34 89 2f 71 00 00 00 00 00 28 00 00 00 0b 00 00 00 76 05 00 00 00 00 00 80 1.... at .4./q.....(.......v.......
> 00003020: 00 00 00 00 00 00 00 00 31 18 10 06 74 7c 20 ed 00 00 00 00 00 00 00 00 1c 00 00 00 05 00 00 00 ........1...t| .................
> 00003040: bc 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
> 00003060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
__le32 len; 28
__le64 cmt_no; 76 05 00 00 00 00 00 80
__le64 inos[]; 0 <----- !!!!!
<snip>
> 00004000: 31 18 10 06 43 37 1d 7e 00 73 77 00 00 00 00 00 28 00 00 00 0b 00 00 00 7d 05 00 00 00 00 00 80 1...C7.~.sw.....(.......}.......
> 00004020: 01 00 00 00 00 00 00 00 31 18 10 06 74 7c 20 ed 00 00 00 00 00 00 00 00 1c 00 00 00 05 00 00 00 ........1...t| .................
> 00004040: bc 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
> 00004060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
__le32 len; 28
__le64 cmt_no; 7d 05 00 00 00 00 00 80
__le64 inos[]; 1 <----- !!!!!
<snip>
> 00005000: 31 18 10 06 86 67 56 c0 53 c8 7d 00 00 00 00 00 28 00 00 00 0b 00 00 00 84 05 00 00 00 00 00 80 1....gV.S.}.....(...............
> 00005020: 8a 18 11 00 00 00 00 00 31 18 10 06 74 7c 20 ed 00 00 00 00 00 00 00 00 1c 00 00 00 05 00 00 00 ........1...t| .................
> 00005040: bc 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
> 00005060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................................
__le32 len; 28
__le64 cmt_no; 84 05 00 00 00 00 00 80
__le64 inos[]; 11188a
<snip>
> 00006000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................................
<snip>
> UBIFS: recovery completed
> UBIFS: mounted UBI device 1, volume 1, name "datafs"
> UBIFS: file system size: 640475136 bytes (625464 KiB, 610 MiB, 1241 LEBs)
> UBIFS: journal size: 10452992 bytes (10208 KiB, 9 MiB, 21 LEBs)
> UBIFS: media format: w4/r0 (latest is w4/r0)
> UBIFS: default compressor: lzo
> UBIFS: reserved for root: 0 bytes (0 KiB)
> UBIFS error (pid 1): ubifs_iget: failed to read inode 1, error -2
> ubifs_fill_super couldn't read UBIFS_ROOT_INO
>
More information about the linux-mtd
mailing list