From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from smtp.nokia.com ([192.100.105.134] helo=mgw-mx09.nokia.com)
	by bombadil.infradead.org with esmtps (Exim 4.68 #1 (Red Hat Linux))
	id 1Jvr5a-0001JR-LV
	for linux-mtd@lists.infradead.org; Tue, 13 May 2008 09:46:30 +0000
Subject: Re: ubifs image file confusion!
From: Artem Bityutskiy <dedekind@infradead.org>
To: Nancy <nancydreaming@gmail.com>
In-Reply-To: <bae050c10805092120u14177a03td46fa8175f89aa66@mail.gmail.com>
References: <bae050c10805080217r77c9724aya0777ccf5f59a293@mail.gmail.com>
	<1210243730.3645.66.camel@sauron>
	<bae050c10805090005g50b657c2jf8d471cd51244da7@mail.gmail.com>
	<bae050c10805092120u14177a03td46fa8175f89aa66@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Date: Tue, 13 May 2008 12:44:21 +0300
Message-Id: <1210671861.5708.5.camel@sauron>
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Reply-To: dedekind@infradead.org
List-Id: Linux MTD discussion mailing list <linux-mtd.lists.infradead.org>
List-Unsubscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
	<mailto:linux-mtd-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/linux-mtd>
List-Post: <mailto:linux-mtd@lists.infradead.org>
List-Help: <mailto:linux-mtd-request@lists.infradead.org?subject=help>
List-Subscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
	<mailto:linux-mtd-request@lists.infradead.org?subject=subscribe>

On Sat, 2008-05-10 at 12:20 +0800, Nancy wrote:
>        ubifs.img (generated by mkfs.ubifs) do contained unmapped LEBs.

This statement does not make sense. Mapped/unmapped is UBI notion, not
UBIFS.

>        #ubiupdatevol /dev/ubi0_0 ubifs.img   also write the unmapped
> LEBs to Nand flash.
It does not write them, but it creates them if the image size is less
then amount of space on the volume. What else do you expect?

>        Oh, There should have the same problem like I use nandwrite to
> write UBI image to Nand. But the practice tells everything is OK.

No, ubiupdatevol handles 0xFFs just fine.

> Example 2 shows
>        ubiupdatevol: error!: specify UBI device name and image file
> name as first 2 par
> ameters (use -h for help)
>        but
>        #ubiupdatevol /dev/ubi0_0 ubifs.img -t
>        instead, even the function do not need an input image file

Fixed, thanks for report.

--=20
Best regards,
Artem Bityutskiy (=D0=91=D0=B8=D1=82=D1=8E=D1=86=D0=BA=D0=B8=D0=B9 =D0=90=
=D1=80=D1=82=D1=91=D0=BC)