From: Richard Weinberger <richard@nod.at>
To: Bhuvanchandra DV <bhuvanchandradv@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS errors when file-system is full
Date: Wed, 22 Jul 2015 09:20:39 +0200 [thread overview]
Message-ID: <55AF4447.50500@nod.at> (raw)
In-Reply-To: <55AF41DD.2060902@gmail.com>
Am 22.07.2015 um 09:10 schrieb Bhuvanchandra DV:
> On 07/21/2015 11:44 AM, Richard Weinberger wrote:
>
>> Hi!
>>
>> Am 21.07.2015 um 08:04 schrieb Bhuvanchandra DV:
>>> Ran the power cut tests with fm_debug enabled, no additional logs are observed.
>>> After few hundred power cuts U-Boot fails to mount with -22 and kernel fails
>>> mounting with stack trace when reading the node.
>> Why U-Boot? Has U-Boot fastmap enabled?
>
> Yes, fastmap is enabled in U-Boot.
Please disable it.
> The same power cut tests are done by skipping the U-Boot to mount the UBIFS. Loaded
> the kernel via tftp and mount the rootfs with kernel. The power cut test passed.
> I think U-Boot might have some issues, but not very sure.
To my knowledge U-Boot's fastmap support is incomplete.
If you *really* need fastmap in U-Boot make sure that they have backported
all recent fastmap changes. Fastmap is still experimental and faced a lot of fixes
recently.
>>
>> Anyway, we need to sort out what is going on.
>> As fm_debug does not trigger it could also be a non-fastmap issue.
>> Did you try your test without fastmap being enabled?
>>
>> Does your target pass UBI tests too?
>
> I'm not aware of UBI tests so far the driver passed all MTD tests.
> Can you please provide some pointers for UBI tests. Will run the UBI tests with
> driver.
They are in the mtd-utils source.
>>
>>> Log:
>> [...]
>>> [ 2.847326] UBIFS error (ubi0:0 pid 1): ubifs_read_node: bad node type (255 but expected 3)
>>> [ 2.866839] UBIFS error (ubi0:0 pid 1): ubifs_read_node: bad node at LEB 981:70368, LEB mapping status 1
>>> [ 2.887961] Not a node, first 24 bytes:
>>> [ 2.891864] 00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ........................
>> Hmm, LEB1 is unmapped.
>> If you disable fastmap, does this target boot as expected?
>> Or is this a persistent corruption?
>
> No, the corruption is persistent.
> - removed|fm_autoconvert from kernel args - removed the fastmap support from kernel Tested with above both cases, the corruption is persistent. |
Okay that is a clear hint that Linux's fastmap is only the messenger and not the evil doer.
Thanks,
//richard
next prev parent reply other threads:[~2015-07-22 7:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 13:55 UBIFS errors when file-system is full Bhuvanchandra DV
2015-07-13 14:09 ` Richard Weinberger
2015-07-14 4:23 ` Bhuvanchandra DV
2015-07-14 6:13 ` Richard Weinberger
2015-07-14 6:30 ` Bhuvanchandra DV
2015-07-14 6:32 ` Richard Weinberger
2015-07-14 8:29 ` Bhuvanchandra DV
2015-07-14 8:42 ` Richard Weinberger
2015-07-14 10:08 ` Bhuvanchandra DV
2015-07-14 11:06 ` Richard Weinberger
[not found] ` <55A74812.2020906@gmail.com>
2015-07-16 7:35 ` Fwd: " Bhuvanchandra DV
[not found] ` <55A74AA1.2000000@nod.at>
[not found] ` <55A7540C.3050900@nod.at>
[not found] ` <55A7592D.6010906@gmail.com>
[not found] ` <55A75A05.7040603@nod.at>
2015-07-16 7:33 ` Bhuvanchandra DV
2015-07-21 6:04 ` Bhuvanchandra DV
2015-07-21 6:14 ` Richard Weinberger
2015-07-22 7:10 ` Bhuvanchandra DV
2015-07-22 7:20 ` Richard Weinberger [this message]
2015-07-24 14:43 ` Bhuvanchandra DV
2015-07-24 16:51 ` Richard Weinberger
2015-07-31 16:47 ` Bhuvanchandra DV
2015-08-01 6:36 ` Richard Weinberger
2015-08-06 10:31 ` Bhuvanchandra DV
2015-08-07 12:37 ` Richard Weinberger
2015-08-12 7:01 ` Stefan Agner
2015-08-12 7:27 ` Richard Weinberger
2015-09-01 0:45 ` Stefan Agner
2015-09-01 1:43 ` Brian Norris
2015-09-01 2:20 ` Stefan Agner
2015-09-02 19:58 ` Stefan Agner
2015-09-02 20:13 ` Brian Norris
2015-09-02 20:41 ` Stefan Agner
2015-09-07 13:47 ` Bhuvanchandra
2015-09-11 4:03 ` Bhuvanchandra
2015-09-12 9:39 ` Richard Weinberger
2015-09-13 4:45 ` Bhuvanchandra
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=55AF4447.50500@nod.at \
--to=richard@nod.at \
--cc=bhuvanchandradv@gmail.com \
--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 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.