mkfs.ubifs problem when output file really isn't in the UBIFS root directory

[Artem Bityutskiy]

Yeah, I am probably confused.

On Mon, 2012-10-08 at 17:04 +0200, Marcus Prebble wrote:
> We have remounted a static UBI volume which happens to be the rootfs (/)
> onto another location, /tmp/newrootfs

So, you have your UBI volume, it contains your root file-sytem, right?
Then you "remount your" root to /tmp/newrootfs? If yes, I would like to
understand how exactly you do this? Give some more details.

> We are trying to make an image of /tmp/newrootfs with mkfs.ubifs and
> where the output file is /tmp/newrootfs.img.


If the inode number of / is the same as /tmp/newroofs, and the device
number is the same, this is the same inode, no?

This means that /tmp/newrootfs.img will also be visible
in /tmp/newrootfs/tmp/newrootfs.img, no?

-- 
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20121010/a6c590f6/attachment-0001.sig>