All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brokhman, Tanya" <tlinder@codeaurora.org>
To: Richard Weinberger <richard.weinberger@gmail.com>,
	Smitha Rathnam <rathnam.smitha@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Trouble with UBIFS
Date: Wed, 10 Jun 2015 14:55:38 +0300	[thread overview]
Message-ID: <557825BA.6030104@codeaurora.org> (raw)
In-Reply-To: <CAFLxGvzA8N4PUK_7-jM9FcnrqLnyOsNcomfLOSMMGKc5Ed5D9Q@mail.gmail.com>

Hi Richard

On 6/10/2015 2:25 PM, Richard Weinberger wrote:
> Hi!
>
> On Wed, Jun 10, 2015 at 12:08 PM, Smitha Rathnam
> <rathnam.smitha@gmail.com> wrote:
>>   Hi,
>>
>>   We have an embedded linux (2.6) system. Since the past few months, we
>> have been seeing a corruption of the log filesystem.
>>   The filesystem is using mtd5 device.
>>   The error looks like this;
>>   user.notice kernel: klogd started: BusyBox v1.20.0 (2012-09-18 17:42:52 MST)
>>
>>   Jan  1 00:00:05 user.debug kernel: 00001fa0: 00000000 00000000
>> 00000000 00000000 00000000 00000000 00000000 00000000
>> ................................
>>   Jan  1 00:00:05 user.debug kernel: 00001fc0: 00000000 00000000
>> 00000000 00000000 00000000 00000000 00000000 00000000
>> ................................
>>   Jan  1 00:00:05 user.debug kernel: 00001fe0: 00000000 00000000
>> 00000000 00000000 00000000 00000000 00000000 00000000
>> ................................
>>   *Jan  1 00:00:05 user.err kernel: UBIFS error (pid 1110):
>> ubifs_recover_leb: LEB 24 scanning failed*
>>
>>   Is there a way to retrieve data from the partition? How do we fix this error?
> To fix the problem one has to analyze it first.
> The kernel output you've posted is incomplete and most likely unrelated.
> Do you have a complete kernel log?
>
> Retrieving data from the filesystem is not easy, it depends how much UBIFS
> is corrupted.
> What I do in such cases is dumping all nodes and running them thought a
> semi-automated script which can deal with UBIFS.
Could you please share the script? I'm facing same issues at the moment 
(debugging ubifs corruption). I have a binary dump of the partition. 
Looking for the most user-friendly tool to look at it.

Thanks
-Tanya

  reply	other threads:[~2015-06-10 11:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 10:08 Trouble with UBIFS Smitha Rathnam
2015-06-10 11:25 ` Richard Weinberger
2015-06-10 11:55   ` Brokhman, Tanya [this message]
2015-06-10 12:43     ` Richard Weinberger
2015-06-10 12:54       ` Brokhman, Tanya
2015-06-11  4:58 ` Smitha Rathnam
2015-06-11  6:39   ` 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=557825BA.6030104@codeaurora.org \
    --to=tlinder@codeaurora.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rathnam.smitha@gmail.com \
    --cc=richard.weinberger@gmail.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.