Re: UBIFS CRC error, calculated from ubifs_check_node

[Tanya Brokhman <tlinder@codeaurora.org>]

On 4/21/2014 12:30 AM, Richard Weinberger wrote:
> Am 20.04.2014 23:24, schrieb Tanya Brokhman:
>> On 4/20/2014 11:55 PM, Richard Weinberger wrote:
>>> On Sun, Apr 20, 2014 at 8:39 PM, Tanya Brokhman <tlinder@codeaurora.org> wrote:
>>>> Hi All
>>>>
>>>> I'm hitting "UBIFS error (pid 1026): ubifs_check_node: bad CRC: calculated
>>>> 0x79dbca01, read 0x31afb5d7" and as a result the partition is remounted as
>>>> RO.
>>>>
>>>> I'm using 3.10 based kernel.
>>>> The test scenario to reproduce this is:
>>>> 1. fill the partition tested using dd
>>>> 2. try to write some more data
>>>>
>>>> There are no errors in the log from the ubi layer or from the underlying
>>>> nand driver, both also testing crc.
>>>>
>>>> I've tried disabling compression, mounting the partition as sync and issuing
>>>> the write command with sync param. None of the former has any effect on this
>>>> crash.
>>>> I tried disabling crc on data nodes. This lowered the possibility of hitting
>>>> the above error but eventually, with stress test of concurrent read and
>>>> write we hit the same error with a different node type.
>>>>
>>>> Has any one encountered similar behavior? I'm not that much familiar with
>>>> ubifs so any help will be highly apritiated!
>>>
>>> Before we start digging into this, do mtd-tests and ubi-tests pass?
>>>
>>
>>
>> mtd-tests: yes.
>
> Good. :)
>
>> ubi-tests: never run those. Where can I find them? I see only debug.c at mtd/ubi with helping functions but no tests.
>>
>> We're just switching to ubifs from yaffs2. I looked at the diff between linux-next and our branch (3.10 based) and tried to bring in all of the fixes in mtd and ubi layers.
>> I'll try running ubi-tests and update on the result.
>>
>> Do you think we should run ubifs tests as well? Are there such tests?
>
> Yes. Fetch mtd-utils source.
> See tests/ubi-tests directory.
> It contains UBI and UBIFS tests.
>
> Please run first ubi tests (runtests.sh).
>
> Thanks,
> //richard
>

Hi Richard

Eventually it turned out to be driver issue. Thank you for your help!

- Tanya

-- 
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation