From: Artem Bityutskiy <dedekind1@gmail.com>
To: Reginald Perrin <reggyperrin@yahoo.com>
Cc: MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS Corruption
Date: Thu, 08 Dec 2011 23:42:32 +0200 [thread overview]
Message-ID: <1323380555.2074.3.camel@koala> (raw)
In-Reply-To: <1323278383.39855.YahooMailNeo@web114617.mail.gq1.yahoo.com>
Hi,
On Wed, 2011-12-07 at 09:19 -0800, Reginald Perrin wrote:
> Booting shows:
> [ 4.860000] UBI: background thread "ubi_bgt1d" started, PID 355
> UBI device number 1, total 749 LEBs (96638976 bytes, 92.2 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
> [ 5.004000] UBIFS: recovery needed
> [ 5.580000] UBIFS error (pid 357): ubifs_recover_leb: garbage
> [ 5.584000] UBIFS error (pid 357): ubifs_scanned_corruption: corruption at LEB 498:81920
> [ 5.588000] UBIFS error (pid 357): ubifs_scanned_corruption: first 8192 bytes from LEB 498:81920
> [ 5.616000] UBIFS error (pid 357): ubifs_recover_leb: LEB 498 scanning failed
Sorry, but I believe I sent you the solution - make the logbuffer larger
and add the ignore debuglevel option. Citing myself:
"log_buf_len=64M
Also add
ignore_loglevel"
IOW, add "log_buf_len=64M ignore_loglevel" options to you kernel boot
options.
Artem.
What is your flash exactly?
Artem.
next prev parent reply other threads:[~2011-12-08 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 13:12 UBIFS Corruption Reginald Perrin
2011-07-18 11:33 ` Artem Bityutskiy
2011-07-19 20:47 ` Reginald Perrin
2011-07-26 19:17 ` Reginald Perrin
2011-08-02 16:14 ` Reginald Perrin
2011-08-15 12:30 ` Artem Bityutskiy
2011-08-15 12:29 ` Artem Bityutskiy
2011-11-28 20:04 ` Reginald Perrin
2011-11-29 22:30 ` Artem Bityutskiy
2011-12-07 17:19 ` Reginald Perrin
2011-12-08 21:42 ` Artem Bityutskiy [this message]
2011-12-12 14:29 ` Reginald Perrin
2011-12-12 16:34 ` Artem Bityutskiy
[not found] ` <1323709988.3066.YahooMailNeo@web114618.mail.gq1.yahoo.com>
2011-12-13 16:25 ` Reginald Perrin
2011-12-13 20:19 ` Artem Bityutskiy
2011-07-18 11:38 ` 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=1323380555.2074.3.camel@koala \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=reggyperrin@yahoo.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;
as well as URLs for NNTP newsgroup(s).