From: Artem Bityutskiy <dedekind1@gmail.com>
To: Micah Anderson <micah@riseup.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS error (pid 564): read_znode: bad indexing node at LEB 484:66064, error 2
Date: Fri, 16 Nov 2012 10:31:06 +0200 [thread overview]
Message-ID: <1353054666.3618.6.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <87625h85fd.fsf@minnow.riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
On Wed, 2012-11-07 at 16:32 -0500, Micah Anderson wrote:
> I had a power outage yesterday. When things came back and I tried to
> boot my guruplug, I am not getting the following:
>
> [ 97.273764] UBIFS error (pid 564): read_znode: bad indexing node at LEB 484:66064, error 2
> [ 97.282188] UBIFS warning (pid 564): ubifs_ro_mode: switched to read-only mode, error -22
> [ 97.290431] UBIFS error (pid 564): ubifs_budget_space: cannot budget space, error -22
I'd need to see entire log, no -ENOCLUE with this amount of input.
> The filesystem is read-only and I can't seem to figure out how to get it
> out of this state. As far as I can tell, there is no fsck.ubifs and I'm
> at a loss at how to get things back to a reasonable state. I found the
> 'nandtest' command, which might be useful for mapping out bad areas, but
> I'm not going to run that without a better clue at how likely I am to
> brick things.
No, there is no recovery program, the file-system is supposed to always
be mountable. Please, use mtdtests to validate the HW:
http://www.linux-mtd.infradead.org/doc/general.html#L_mtd_tests
--
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-11-16 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 21:32 UBIFS error (pid 564): read_znode: bad indexing node at LEB 484:66064, error 2 Micah Anderson
2012-11-16 8:31 ` Artem Bityutskiy [this message]
2012-11-16 16:09 ` micah anderson
2012-11-16 21:20 ` micah anderson
2012-11-30 9:04 ` Artem Bityutskiy
2012-11-30 9:00 ` 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=1353054666.3618.6.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=micah@riseup.net \
/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