From: Artem Bityutskiy <dedekind1@gmail.com>
To: Eric Millbrandt <emillbrandt@dekaresearch.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: ubi volume unmountable after power cut
Date: Fri, 19 Aug 2011 15:11:54 +0300 [thread overview]
Message-ID: <1313755918.6607.56.camel@sauron> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD32A723D86B0@dekaexchange07.deka.local>
On Wed, 2011-08-10 at 15:46 -0400, Eric Millbrandt wrote:
> All,
>
> One of our systems came back "unbootable" from our QA department.
> When I took a look at the system I found that the rootfs, which is a
> ubi/ubifs filesystem, had become corrupt. My QA department swears
> that they powered off the system correctly, but even so, shouldn't ubi
> be tolerant of power cuts? I've attached all the relevant information
> below.
>
> # uname -r
> 2.6.33.7-rt29-deka-debug
I strongly recommend you to pull in changes from the UBIFS back-port
trees.
> [ 140.482974] UBI error: ubi_io_read: error -74 while reading 516096
> bytes from PEB 3889:8192, read 516096 bytes
> [ 140.494658] Call Trace:
> [ 140.497406] [cf86fac0] [c00097bc] show_stack+0x4c/0x16c
> (unreliable)
> [ 140.504881] [cf86fb00] [c031f298] ubi_io_read+0x170/0x28c
> [ 140.511141] [cf86fb40] [c031e4a8] ubi_eba_read_leb+0x13c/0x36c
> [ 140.517961] [cf86fb80] [c031c7bc] ubi_leb_read+0x120/0x170
> [ 140.524329] [cf86fbb0] [c01edd64] ubifs_start_scan+0xb8/0x1e8
> [ 140.531053] [cf86fbe0] [c0205820] ubifs_recover_leb+0x68/0xa78
> [ 140.537876] [cf86fc50] [c01eead0] replay_buds+0xa8/0xcf4
> [ 140.544052] [cf86fcf0] [c01f0018] ubifs_replay_journal+0x8fc/0x1284
> [ 140.551315] [cf86fd80] [c01e1268] ubifs_fill_super+0xf20/0x1928
> [ 140.558225] [cf86fde0] [c01e2638] ubifs_get_sb+0x104/0x384
> [ 140.564702] [cf86fe60] [c00c8d18] vfs_kern_mount+0x70/0x190
> [ 140.571142] [cf86fe90] [c00c8e88] do_kern_mount+0x40/0x100
> [ 140.577501] [cf86feb0] [c00e3030] do_mount+0x4d8/0x828
> [ 140.583497] [cf86ff10] [c00e3410] sys_mount+0x90/0xd0
> [ 140.589399] [cf86ff40] [c0012f2c] ret_from_syscall+0x0/0x38
> [ 140.595950] --- Exception: c01 at 0xfdd64c8
> [ 140.595964] LR = 0x10063dd8
> [ 140.606215] UBIFS error (pid 361): ubifs_recover_leb: garbage
> [ 140.612939] UBIFS error (pid 361): ubifs_scanned_corruption:
> corruption at LEB 3211:335872
> [ 140.622385] UBIFS error (pid 361): ubifs_scanned_corruption: first
> 8192 bytes from LEB 3211:335872
> [ 140.646492] UBIFS error (pid 361): ubifs_recover_leb: LEB 3211
> scanning failed
Please, produce the issue and send all messages, not only error messages
which you see on your console. E.g, send dmesg output. It is difficult
to say anything without the full log which should contain flash dump.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-08-19 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 19:46 ubi volume unmountable after power cut Eric Millbrandt
2011-08-12 15:25 ` Matthieu CASTET
2011-08-19 12:11 ` Artem Bityutskiy [this message]
2011-08-19 13:42 ` Eric Millbrandt
2011-08-19 15:16 ` Artem Bityutskiy
2011-08-19 17:50 ` Eric Millbrandt
2011-08-22 13:43 ` Artem Bityutskiy
2011-08-22 14:28 ` Eric Millbrandt
2011-08-22 14:35 ` Artem Bityutskiy
2011-08-22 14:40 ` Eric Millbrandt
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=1313755918.6607.56.camel@sauron \
--to=dedekind1@gmail.com \
--cc=emillbrandt@dekaresearch.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