From: tommy <jiujin.hong@mid-fun.com>
To: linux-mtd@lists.infradead.org
Subject: about ubiformat mtdblock
Date: Fri, 26 Jun 2009 18:03:12 +0800 [thread overview]
Message-ID: <1246010592.12367.0.camel@tommy-desktop> (raw)
hi,dear all!
My kernel version is 2.6.24 ,patch ubifs !
I met error on ubiformat .
Following is my step!
# ./ubiformat /dev/mtd2 -f /ubi.img
ubiformat: mtd2 (NAND), size 654311424 bytes (624.0 MiB), 262144
eraseblocks of 262144 bytes (256.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 2495 -- 100 % complete
ubiformat: 2496 eraseblocks have valid erase counter, mean value is 0
ubiformat: flashing eraseblock 383 -- 100 % complete
ubiformat: formatting eraseblock 2495 -- 100 % complete
# ./ubiattach /dev/ubi_ctrl -m 2
vmalloc is used.
UBI: physical eraseblock size: 262144 bytes (256 KiB)
UBI: logical eraseblock size: 258048 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: volume 0 ("ubifs0") re-sized from 407 to 2468 LEBs
UBI: attached mtd2 to ubi0
UBI: MTD device name: "File System"
UBI: MTD device size: 624 MiB
UBI: number of good PEBs: 2496
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: 0
UBI: total number of reserved PEBs: 2496
UBI: number of PEBs reserved for bad PEB handling: 24
UBI: max/mean erase counter: 2/1
UBI: background thread "ubi_bgt0d" started, PID 306
UBI device number 0, total 2496 LEBs (644087808 bytes, 614.2 MiB),
available 0 LEBs (0 bytes), LEB size 258048 bytes (252.0 KiB)
# mount -t ubifs ubi0_0 /tmp/
UBIFS error (pid 307): ubifs_read_superblock: on-flash format version
is 4, but software only supports up to version 3
mount: mounting ubi0_0 on /tmp/ failed: Invalid argument
can anyone help me ?thanks!
next reply other threads:[~2009-06-26 10:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 10:03 tommy [this message]
2009-06-26 10:46 ` about ubiformat mtdblock Artem Bityutskiy
2009-06-27 3:49 ` tommy
2009-06-27 11:32 ` Artem Bityutskiy
2009-06-29 2:14 ` tommy
2009-06-30 14:51 ` Artem Bityutskiy
2009-07-01 0:54 ` tommy
2009-07-01 9:50 ` Artem Bityutskiy
2009-07-01 10:43 ` tommy
2009-07-01 10:45 ` Artem Bityutskiy
2009-07-01 10:58 ` tommy
2009-07-01 11:06 ` Artem Bityutskiy
2009-07-01 11:13 ` tommy
2009-07-02 9:39 ` tommy
[not found] ` <d16af8a00907020255r60112844qbb7f020afd9a1ac0@mail.gmail.com>
2009-07-02 10:13 ` tommy
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=1246010592.12367.0.camel@tommy-desktop \
--to=jiujin.hong@mid-fun.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