From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] UBIFS fails on SheevaPlug
Date: Tue, 30 Oct 2012 00:55:49 +0100 [thread overview]
Message-ID: <508F1785.4020109@googlemail.com> (raw)
In-Reply-To: <CAF9kqNFu=ZTZkYX0Heo3u_DvwRLoVxrrXLd60U689RyfwG2_kQ@mail.gmail.com>
Dear Dimax,
On 29.10.2012 20:05, Dimax wrote:
>> U-boot will _not_ recover your UBIFS partition like the Linux kernel.
> CMIIW.
> In other words it is not possible to use UBIFS on embedded Linux boards
> with u-boot unless you can provide unterminated power supply.
NAK
I invested some time to reproduce this, however see following scenario:
---8<---
DockStar> ubi part root; ubifsmount root
Creating 1 MTD partitions on "nand0":
0x000000100000-0x000010000000 : "mtd=1"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=1"
UBI: MTD device size: 255 MiB
UBI: number of good PEBs: 2040
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 20
UBI: total number of reserved PEBs: 2020
UBI: number of PEBs reserved for bad PEB handling: 20
UBI: max/mean erase counter: 4/2
UBIFS: recovery needed
UBIFS error (pid 0): ubifs_mount: Error reading superblock on volume
'ubi:root' errno=-12!
ubifsmount - mount UBIFS volume
Usage:
ubifsmount <volume-name>
- mount 'volume-name' volume
DockStar> ver
U-Boot 2012.10 (Oct 30 2012 - 00:46:13)
Seagate FreeAgent DockStar
arm-v5te-linux-gnueabi-gcc (OSELAS.Toolchain-2011.11.0) 4.6.2
GNU ld (GNU Binutils) 2.21.1
DockStar>
--->8---
---8<---
DockStar> ubi part root; ubifsmount root
Creating 1 MTD partitions on "nand0":
0x000000100000-0x000010000000 : "mtd=1"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=1"
UBI: MTD device size: 255 MiB
UBI: number of good PEBs: 2040
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 20
UBI: total number of reserved PEBs: 2020
UBI: number of PEBs reserved for bad PEB handling: 20
UBI: max/mean erase counter: 4/2
UBIFS: recovery needed
UBIFS: recovery deferred
UBIFS: mounted UBI device 0, volume 0, name "root"
UBIFS: mounted read-only
UBIFS: file system size: 255854592 bytes (249858 KiB, 244 MiB, 1983 LEBs)
UBIFS: journal size: 12773376 bytes (12474 KiB, 12 MiB, 99 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: LZO
UBIFS: reserved for root: 5182151 bytes (5060 KiB)
DockStar> ver
U-Boot 2012.10-00001-g65cc68e (Oct 30 2012 - 00:50:51)
Seagate FreeAgent DockStar
arm-v5te-linux-gnueabi-gcc (OSELAS.Toolchain-2011.11.0) 4.6.2
GNU ld (GNU Binutils) 2.21.1
DockStar>
--->8---
---8<---
andreas at andreas-pc % git describe
v2012.10-1-g65cc68e
andreas at andreas-pc % git show
| commit 65cc68eb06df0c957a17a611bc3f3756e91108b2 (HEAD, test-malloc)
| Author: Andreas Bie?mann <andreas.devel@googlemail.com>
| Date: Mon Oct 29 21:36:53 2012 +0100
|
| mv-common.h: increase malloc arena to 4MiB
|
| Signed-off-by: Andreas Bie?mann <andreas.devel@googlemail.com>
|
| diff --git a/include/configs/mv-common.h b/include/configs/mv-common.h
| index 7086d1d..405a842 100644
| --- a/include/configs/mv-common.h
| +++ b/include/configs/mv-common.h
| @@ -92,7 +92,7 @@
| /*
| * Size of malloc() pool
| */
| -#define CONFIG_SYS_MALLOC_LEN (1024 * 1024) /* 1MiB for malloc() */
| +#define CONFIG_SYS_MALLOC_LEN (1024 * 1024 * 4) /* 4MiB for malloc() */
|
| /*
| * Other required minimal configurations
--->8---
Best regards
Andreas Bie?mann
next prev parent reply other threads:[~2012-10-29 23:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 14:48 [U-Boot] UBIFS fails on SheevaPlug Dimax
2012-10-28 22:54 ` Marek Vasut
2012-10-29 5:25 ` Dimax
2012-10-29 6:38 ` Dimax
2012-10-29 6:48 ` Andreas Bießmann
2012-10-29 6:55 ` Dimax
2012-10-29 8:38 ` Andreas Bießmann
2012-10-29 8:50 ` Dimax
2012-10-29 9:11 ` Andreas Bießmann
2012-10-29 9:27 ` Dimax
2012-10-29 9:43 ` Andreas Bießmann
2012-10-29 10:19 ` Marek Vasut
2012-10-29 10:34 ` Andreas Bießmann
2012-10-29 16:02 ` Vikram Narayanan
2012-10-29 12:15 ` Prafulla Wadaskar
2012-10-29 17:25 ` Dimax
2012-10-29 18:53 ` Vikram Narayanan
2012-10-29 19:05 ` Dimax
2012-10-29 23:55 ` Andreas Bießmann [this message]
2012-10-29 23:02 ` Andreas Bießmann
2012-10-31 16:27 ` Vikram Narayanan
2012-10-31 16:50 ` Andreas Bießmann
2012-10-31 16:55 ` Vikram Narayanan
2012-10-31 17:23 ` Dimax
2012-10-31 17:56 ` Andreas Bießmann
2012-10-31 20:45 ` [U-Boot] How to enable debug information in u-boot Paulo Louro
2012-11-06 7:51 ` [U-Boot] UBIFS fails on SheevaPlug Dimax
2012-11-06 9:12 ` Andreas Bießmann
2012-11-12 5:33 ` Dimax
2012-11-12 8:33 ` Andreas Bießmann
2012-11-12 16:55 ` Dimax
2012-11-12 17:15 ` Vikram Narayanan
2012-10-29 6:01 ` Prafulla Wadaskar
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=508F1785.4020109@googlemail.com \
--to=andreas.devel@googlemail.com \
--cc=u-boot@lists.denx.de \
/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.