All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@sigma-star.at>
To: "Sourabh Jain (R&D - Telecom)" <sourabh.jain@matrixcomsec.com>,
	"linux-mtd @ lists . infradead . org"
	<linux-mtd@lists.infradead.org>
Cc: "Vamsi S (R&D - Telecom)" <vamsi.s@matrixcomsec.com>,
	"Rajdeep Vaghasia (Software Development - Telecom)"
	<rajdeep.vaghasia@matrixcomsec.com>,
	"Shailesh Panchal (Software Development - Telecom)"
	<shailesh.panchal@matrixcomsec.com>
Subject: Re: UBIFS node corruption issue
Date: Fri, 01 Jun 2018 14:49:56 +0200	[thread overview]
Message-ID: <2203231.iLWHeG1VOg@blindfold> (raw)
In-Reply-To: <CAAR3sxPDomY9SzdUt=FAJsaMFUqJMpDviNc4dFbz4WZaX8f8oQ@mail.gmail.com>

Am Freitag, 1. Juni 2018, 14:23:05 CEST schrieb Sourabh Jain (R&D - Telecom):
> >> What can be the problem?
> >
> > Well, UBIFS' index tree seems to reference a LEB (or part of a LEB)
> > which is empty.
> > This can have tons of reasons. Starting from MTD drivers bugs to UBIFS bugs.
> 
> There is one observation, i have read all the VID header from the PEB
> and there is
> no header having LEB number 328, which causing problem.
> Why there is mapping for LEB Number 328 in index tree?

Depends. Maybe the PEB behind the LEB was erased by mistake.
I have seen such driver bugs.
 
> 
> >> How we can resolve this issue?
> >>
> >> Please suggest us necessary action to be taken. Also, please inform us
> >> if any further input is required from us.
> >
> > Are you facing this problem on more than one target, and is it reproducible?
> 
> We are facing this problem in some boards.
> there is another problem in which the root file system become read
> only but actually it is r/w.

Do you face this issues also on a recent kernel?

Thanks,
//richard

-- 
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y

  reply	other threads:[~2018-06-01 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01  4:25 UBIFS node corruption issue Sourabh Jain (R&D - Telecom)
2018-06-01  8:28 ` Richard Weinberger
2018-06-01 12:23   ` Sourabh Jain (R&D - Telecom)
2018-06-01 12:49     ` Richard Weinberger [this message]
     [not found] <d03e8f457821494f951fabac2933bbfe@SIWEX5A.sing.micron.com>
2018-06-15  6:27 ` Richard Weinberger
2018-06-15  7:19   ` Sourabh Jain (R&D - Telecom)
2018-06-15  7:25     ` Richard Weinberger

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=2203231.iLWHeG1VOg@blindfold \
    --to=richard@sigma-star.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rajdeep.vaghasia@matrixcomsec.com \
    --cc=shailesh.panchal@matrixcomsec.com \
    --cc=sourabh.jain@matrixcomsec.com \
    --cc=vamsi.s@matrixcomsec.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.