Yes it's the same problem I faced: the restored ubifs has half the space free. I imagine it's an issue in the way files are compressed. I read there are two compression methods in ubifs. Could it be possible that when restoring the less efficient is used? Can we force the most efficient?

I found very interesting this chapter on lzo vs. zlib compression on ubifs, and the way to use both of them more efficiently: http://www.linux-mtd.infradead.org/f...ml#L_favor_lzo
We might transform the tar rootfs archive in a flashable img selecting either only zlib or a mix of zlib and lzo by using the proper parameter in mkfs.ubifs - see the first post of this thread for the howto.


On another hand, I am trying to fork the old ver 0.32, that as far as I know is the latest using dd to store a filesystem image. Basically, I want to solve the post pr1.3 problem of it not exiting the dd cycle and needing to pull the battery out to stop. In my hands, ver 0.32 has worked much better than the following tar based versions. With tar, several times I've had a broken restore of the optfs (stale nfs handle errors). Instead, img restore of optfs has never failed, and for rootfs it's been enough to restore through flashing with an external machine and never try a restore from the N900.

What do you think Robbie?