ubifs issue about ubifs_tnc_remove_ino when replay journal

Sat Jun 25 01:32:31 PDT 2016

-----Original Message-----
From: Richard Weinberger [mailto:richard.weinberger at gmail.com] 
Sent: Saturday, June 25, 2016 4:42 PM
To: 이가람/주임연구원〉SW Platform(연)AOT팀(karam.lee at lge.com) <karam.lee at lge.com>
Cc: linux-mtd at lists.infradead.org; 박승호 <seungho1.park at lge.com>
Subject: Re: ubifs issue about ubifs_tnc_remove_ino when replay journal

On Sat, Jun 25, 2016 at 8:08 AM, 이가람/주임연구원〉SW
Platform(연)AOT팀(karam.lee at lge.com) <karam.lee at lge.com> wrote:
> hi mtd-list
>
> I've seen a problem on embedded board with UBIFS/UBI.
> My environment is as follows:
>
> kernel version : 3.10.49
> flash : 512MB nand, 128KB PEB
>
> If a power cut occurs when the system is operating a problem occur in 
> a journal replay at reboot.
>
> ubifs_jnl_delete_inode or ubifs_jnl_delete_xattr remove all nodes 
> belonging to the extended attribute inode from TNC.
> And it makes the journal to delete the information in flash.
> The journal is applied to flash on reboot.
> However, the GC delete the region before applying journal, I guess 
> that the problem occurs.
>
> ------------------ kernel log -------------------------
> [    3.637490]   No soundcard[    3.644631] UBIFS-0: background thread "ubifs_bgt0_0" started, PID 108
> [    3.675468] UBIFS-0: recovery needed
> [    4.323462] UBIFS-0 error (pid 1): ubifs_read_node: bad node type (192 but expected 3)
> [    4.330341] UBIFS-0 error (pid 1): ubifs_read_node: bad node at LEB 635:58544, LEB mapping status 1
> [    4.339388] Not a node, first 24 bytes:
> [    4.343030] 00000000: 47 5f 49 44 45 4e 54 49 46 49 45 52 3d 6e 65 74 6d 67 72 64 c0 05 fd 04                          G_IDENTIFIER=netmgrd....
> [    4.356051] CPU: 0 PID: 1 Comm: swapper Tainted: G        W    3.10.49+ #1
> [    4.362923] [<c00143b8>] (unwind_backtrace+0x0/0xe0) from [<c00118a8>] (show_stack+0x10/0x14)
> [    4.371419] [<c00118a8>] (show_stack+0x10/0x14) from [<c01ba514>] (ubifs_read_node+0x240/0x27c)
> [    4.380089] [<c01ba514>] (ubifs_read_node+0x240/0x27c) from [<c01d41a4>] (ubifs_tnc_read_node+0x48/0x130)
> [    4.389651] [<c01d41a4>] (ubifs_tnc_read_node+0x48/0x130) from [<c01bb2d4>] (tnc_read_node_nm+0xb4/0x1b8)
> [    4.399196] [<c01bb2d4>] (tnc_read_node_nm+0xb4/0x1b8) from [<c01be624>] (ubifs_tnc_next_ent+0x144/0x18c)
> [    4.408744] [<c01be624>] (ubifs_tnc_next_ent+0x144/0x18c) from [<c01be6b0>] (ubifs_tnc_remove_ino+0x44/0x124)
> [    4.418641] [<c01be6b0>] (ubifs_tnc_remove_ino+0x44/0x124) from [<c01c0c9c>] (ubifs_replay_journal+0xbdc/0x1130)
> [    4.428796] [<c01c0c9c>] (ubifs_replay_journal+0xbdc/0x1130) from [<c01b6a50>] (ubifs_mount+0xb80/0x1568)
> [    4.438352] [<c01b6a50>] (ubifs_mount+0xb80/0x1568) from [<c00d9a40>] (mount_fs+0x10/0xb4)
> [    4.446593] [<c00d9a40>] (mount_fs+0x10/0xb4) from [<c00f11dc>] (vfs_kern_mount+0x48/0xc4)
> [    4.454838] [<c00f11dc>] (vfs_kern_mount+0x48/0xc4) from [<c00f35d4>] (do_mount+0x6a8/0x79c)
> [    4.463258] [<c00f35d4>] (do_mount+0x6a8/0x79c) from [<c00f374c>] (SyS_mount+0x84/0xb8)
> [    4.471245] [<c00f374c>] (SyS_mount+0x84/0xb8) from [<c09cedd4>] (mount_block_root+0xf8/0x274)
> [    4.479824] [<c09cedd4>] (mount_block_root+0xf8/0x274) from [<c09cf124>] (prepare_namespace+0x88/0x1b8)
> [    4.489212] [<c09cf124>] (prepare_namespace+0x88/0x1b8) from [<c09ceb90>] (kernel_init_freeable+0x170/0x1b4)
> [    4.499023] [<c09ceb90>] (kernel_init_freeable+0x170/0x1b4) from [<c06b9c1c>] (kernel_init+0x8/0xe4)
> [    4.508136] [<c06b9c1c>] (kernel_init+0x8/0xe4) from [<c000dc98>] (ret_from_fork+0x14/0x3c)
> [    4.517918] UBIFS-0: background thread "ubifs_bgt0_0" stops
> ------------------ kernel log -------------------------
>
> The following message has been reporting on the mailing list in the past.
> This message is similar to my problem.
>
> 2014 jul 12 ubifs issue about xattr node when replay journal :
> -------------------------------------------
> http://lists.infradead.org/pipermail/linux-mtd/2014-July/054620.html

The author of this thread never answered our question whether Fastmap was in involved or not. Do you use Fastmap?
Just to rule that possibility out.

thank you!

I do not use fastmap. 
My ".config" is "# CONFIG_MTD_UBI_FASTMAP is not set"

--
Thanks,
//richard