All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Krzeminski,
	Marcin (Nokia - PL/Wroclaw)" <marcin.krzeminski@nokia.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS - strange behaviour after enabling chk_index
Date: Fri, 16 Sep 2016 17:59:06 +0200	[thread overview]
Message-ID: <a381b47f-37ab-674a-b9e1-0ff50b84e065@nod.at> (raw)
In-Reply-To: <AM4PR0701MB21307808BDB62C97DB81DCD3FEF00@AM4PR0701MB2130.eurprd07.prod.outlook.com>

Marcin,

On 15.09.2016 08:33, Krzeminski, Marcin (Nokia - PL/Wroclaw) wrote:
>> Is this the SPI-NOR device you talked about on IRC?
> Yes.

The one where you're facing issues after a power cut?

>> Maybe the check is broken, maybe it uncovers a hard to hit issue on your
>> flash. Both could be.
>>
>> Do you emulate exactly the same device in qemu?
> Yes, this part of HW is virtualized in Qemu, in fact the same SW build runs on Qemu and HW.
> Since it reproduce on both it allows to think that this is SW related (at least for now),
> but sure does not mean that this is UBI/UBIFS.
> 
> Back to problem, it seem that this could be a debug facility issue, since file system and data
> are not corrupted. If data on flash are correct (I have done many test and all passed,
> so currently I assume that drier is working properly), it could be that data in debug structure
> in this case are somehow outdated/bad (d->old_zroot).
> In test script, if I copy the same file twice (instead of three times) the problem does not
> reproduce. 
> I will try to debug this more, maybe you have any inside where to look?

I think chk_index exposes the power cut issue you told me on IRC.
For whatever reason the index corrupts on your flash. And chk_index
catches this very early.

Maybe there is an issue in the SPI-NOR code or UBI itself has trouble
with your flash (layout).

Thanks,
//richard

  reply	other threads:[~2016-09-16 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  8:28 UBIFS - strange behaviour after enabling chk_index Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-09-14 21:39 ` Richard Weinberger
2016-09-15  6:33   ` Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-09-16 15:59     ` Richard Weinberger [this message]
2016-09-19  7:36       ` Krzeminski, Marcin (Nokia - PL/Wroclaw)

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=a381b47f-37ab-674a-b9e1-0ff50b84e065@nod.at \
    --to=richard@nod.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marcin.krzeminski@nokia.com \
    /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.