public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: 王丁 <walklook@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: ubifs issue about xattr node when replay journal
Date: Wed, 16 Jul 2014 14:08:53 +0300	[thread overview]
Message-ID: <1405508933.1906.29.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAEGnBBSC=k5kkQYkLn37Q8KLLC+n43KiNr9ZZ-8NPJaGkGf0Qg@mail.gmail.com>

On Sat, 2014-07-12 at 21:36 +0800, 王丁 wrote:
> -------- kernel 3.10 log --------
> [   64.916532] UBIFS: background thread "ubifs_bgt0_16" started, PID 92
> [   64.926411] UBIFS: recovery needed
> [   65.013786] UBIFS error (pid 91): ubifs_read_node: bad node type
> (255 but expected 3)
> [   65.021595] UBIFS error (pid 91): ubifs_read_node: bad node at LEB
> 88:39680, LEB mapping status 1
> [   65.030431] Not a node, first 24 bytes:
> [   65.034073] 00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff

There was a similar report recently (but not about xattr) and I suspect
"fastmap". Please, check if you use it - it is new and I did not see any
report that it was extensively tested WRT power cuts.

-- 
Best Regards,
Artem Bityutskiy

  parent reply	other threads:[~2014-07-16 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 13:36 ubifs issue about xattr node when replay journal 王丁
2014-07-14  9:40 ` hujianyang
2014-07-16 11:08 ` Artem Bityutskiy [this message]
2014-07-16 12:05   ` Richard Weinberger
     [not found] <7590973538024349719@unknownmsgid>
2014-07-16 11:05 ` 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=1405508933.1906.29.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=walklook@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