From: Artem Bityutskiy <dedekind1@gmail.com>
To: James Nute <newten82@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS error: replay_log_leb: first log node at LEB 3:0 is not CS node
Date: Fri, 11 May 2012 17:03:04 +0300 [thread overview]
Message-ID: <1336744984.2625.79.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAEg8X7XO4xgHravjYtswWZ0xh_o2ZvPcsT=iH=-bYoV57+ZE7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
On Wed, 2012-05-09 at 09:45 -0400, James Nute wrote:
> Hello
>
> I'm getting a UBIFS Corruption during a power failure with a fail
> signature that I believe is different from what has been seen in the
> past.
> When I flash a new UBI image onto my device and boot it for the first
> time everything comes up as expected. However if I force a power
> failure before any major file writes occur the device will crash when
> UBIFS attempts to recover during the next reboot. If I force a sync
> command before the power failure I am able to successfully avert the
> recovery failure. I worry that this indicates something ugly is going
> on that I can't detect.
Unfortunately you did not really enable the debugging messages or you
forgot to type "dmesg". Anyway, they are absent.
>
> To get more debug messages I have enabled UBIFS debugging and enabled
> the recovery and mount messages by booting with
> ""ubifs.debug_msgs=6144 ignore_loglevel" kernel parameters
Can you actually enable them and share the log? Or may be you can dump
the image and share it - I should be able to put it to nandsim and try
to mount and see.
Looks like old master node was for some reason selected for some reason
- I'd first looked to the master area. But most probably it was already
cleaned-up when you tried to mounted for the very first time after the
power cut. Do you have kernel logs of that ? Are there messages about
corrupted master node?
Is this problem reproducible?
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-11 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 13:45 UBIFS error: replay_log_leb: first log node at LEB 3:0 is not CS node James Nute
2012-05-11 14:03 ` Artem Bityutskiy [this message]
2012-05-11 18:56 ` James Nute
2012-05-15 7:22 ` Artem Bityutskiy
2012-06-04 20:05 ` James Nute
2012-06-06 9:03 ` Artem Bityutskiy
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=1336744984.2625.79.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=newten82@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox