From: Adrian Hunter <adrian.hunter@nokia.com>
To: jerry <jerrydreaming@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: ubifs corrupt
Date: Tue, 14 Apr 2009 11:32:31 +0300 [thread overview]
Message-ID: <49E44A1F.9000605@nokia.com> (raw)
In-Reply-To: <71103bce0904140105l2aea95b4i2bfe460abacf66ec@mail.gmail.com>
jerry wrote:
> 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.
Do you have this patch?
http://git.infradead.org/ubifs-2.6.git?a=commitdiff;h=de0975781a1a8bc92e07eb7681d10ef9bb5e6df9
next prev parent reply other threads:[~2009-04-14 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 8:05 ubifs corrupt jerry
2009-04-14 8:32 ` Adrian Hunter [this message]
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=49E44A1F.9000605@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=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 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.