linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hujianyang <hujianyang@huawei.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: ubifs: replay log error
Date: Tue, 10 Jun 2014 17:15:20 +0800	[thread overview]
Message-ID: <5396CCA8.7060303@huawei.com> (raw)

Hi Artem,

I meet a serious problem when I was mounting an ubifs partition in v3.10.

[  938.975707] UBIFS: background thread "ubifs_bgt0_0" started, PID 2222
[  938.992994] UBIFS: recovery needed
[  939.005971] UBIFS error (pid 2220): replay_log_leb: first log node at LEB 4:0 is not CS node
[  939.006004] UBIFS error (pid 2220): replay_log_leb: log error detected while replaying the log at LEB 4:0
[  939.006024]  magic          0x6101831
[  939.006046]  crc            0x81e22cd5
[  939.006063]  node_type      8 (reference node)
[  939.006084]  group_type     0 (no node group)
[  939.006105]  sqnum          2375337
[  939.006123]  len            64
[  939.006144]  lnum           5273
[  939.006164]  offs           122880
[  939.006181]  jhead          2
[  939.006279] UBIFS: background thread "ubifs_bgt0_0" stops

I found a similar problem fixed by commit c6727932, Do you think they are
related?

In my environment, system will be shutdown by high temperature. So the
filesystem would be unclean umount several times.

Besides, do we have some tools like fsck to re-valid the partition after
this error happen? I can't mount this partition now and format it again is
the only way I know to deal with this situation.

Thanks.

Hu

             reply	other threads:[~2014-06-10  9:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  9:15 hujianyang [this message]
2014-06-19  8:38 ` ubifs: replay log error hujianyang
2014-06-19  8:57 ` hujianyang
2014-06-24 12:42   ` hujianyang
2014-06-29 13:39   ` Artem Bityutskiy
2014-06-29 14:14     ` 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=5396CCA8.7060303@huawei.com \
    --to=hujianyang@huawei.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).