public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: jerry <jerrydreaming@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: ubifs corrupt
Date: Tue, 14 Apr 2009 16:05:35 +0800	[thread overview]
Message-ID: <71103bce0904140105l2aea95b4i2bfe460abacf66ec@mail.gmail.com> (raw)

Hi Artem,

I'm getting some problem with UBIFS when the power is switched off abruptly
 during a write to flash(nandflash 2k/page). In the next boot the contents of
 the file is not found and prints the following information.

UBIFS error (pid 358): ubifs_check_node: bad magic 0xffffffff,
expected 0x6101831
UBIFS error (pid 358): ubifs_check_node: bad node at LEB 27:251264
UBIFS error (pid 358): ubifs_read_node: expected node type 2
UBIFS error (pid 358): ubifs_check_node: bad magic 0xffffffff,
expected 0x6101831
UBIFS error (pid 358): ubifs_check_node: bad node at LEB 27:251264
UBIFS error (pid 358): ubifs_read_node: expected node type 2
problem renaming the file /Settings/qpe.conf.new to /Settings/qpe.conf
UBIFS error (pid 358): ubifs_check_node: bad magic 0xffffffff,
expected 0x6101831
UBIFS error (pid 358): ubifs_check_node: bad node at LEB 27:251264
UBIFS error (pid 358): ubifs_read_node: expected node type 2

I think the qpe.conf is writting when the power is off and The problem
is reproducable.

Please could you tell me if this is a known issue.

Thanks for your help and time!

Regards,

Jerry

             reply	other threads:[~2009-04-14  8:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14  8:05 jerry [this message]
2009-04-14  8:32 ` ubifs corrupt Adrian Hunter
2009-04-14  9:02 ` Artem Bityutskiy
  -- strict thread matches above, loose matches on Subject: below --
2009-04-28  1:51 jerry
2009-05-05  5:02 ` Artem Bityutskiy
2009-05-06 10:29   ` jerry
2009-05-07  5:15     ` 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=71103bce0904140105l2aea95b4i2bfe460abacf66ec@mail.gmail.com \
    --to=jerrydreaming@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