All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Tanya Brokhman <tlinder@codeaurora.org>
Cc: Dolev Raviv <draviv@codeaurora.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: UBIFS CRC error, calculated from ubifs_check_node
Date: Sun, 20 Apr 2014 23:30:35 +0200	[thread overview]
Message-ID: <53543C7B.5000202@nod.at> (raw)
In-Reply-To: <53543AFC.7050202@codeaurora.org>

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

  reply	other threads:[~2014-04-20 21:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-20 18:39 UBIFS CRC error, calculated from ubifs_check_node Tanya Brokhman
2014-04-20 20:55 ` Richard Weinberger
2014-04-20 21:24   ` Tanya Brokhman
2014-04-20 21:30     ` Richard Weinberger [this message]
2014-04-27 11:19       ` Tanya Brokhman
  -- strict thread matches above, loose matches on Subject: below --
2014-04-20 18:39 Tanya Brokhman

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=53543C7B.5000202@nod.at \
    --to=richard@nod.at \
    --cc=dedekind1@gmail.com \
    --cc=draviv@codeaurora.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tlinder@codeaurora.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.