Notices

can someone help me with that issue?

everytime i use backupmenu to restore after i brick my phone it restores everything exactly as it was exept the rootfs space!!!

before restore i had 70 mb and after it went to 30???

why?

and how can i fix that cause i like backupmenu but i am getting tired of that it eats my precious rootfs space!!!

PLEASE HELP ME!!!

thanks in advance

i am still a noob

sorry

I hate to see people beg for help.

If you want an informed opinion, do a Power Search for Backupmenu and ask the question on a thread where its developer hangs out.When you ask like this, you risk getting answers from riff-raff like me.

hi

i did search for a solution but no one posted yet?

what i could found is that u can make a img file of ur latest rootfs tar file to flash in ur device but as i said i am a noob and dont know how to do that

isn't there a easier way?

i also pm the developer for help and waiting for his reply

May i ask u if u have the same problem with backupmenu?
if yes how or what did u do to get that lost space of rootfs

and at last,,

I am asking for help not BEGGING

thanks in advance

Here is a thread where Robbie hangs out. I found it with power search.

http://talk.maemo.org/showthread.php?t=63975&page=66

I haven't noticed this problem.

The three exclamation points accentuate the begging effect, if you ask me. Just asking a question is usually enough. People usually answer if they know.

30 mb of rootfs is fine, I think. I have less than that. I understand the issue, though.

There is a solution, but it's not that simple, and if you feel you haven't much experience with command line in linux, don't try it home.

Basically, you have to build an ubifs image out of your rootfs tar archive generated by backupmenu. The ubifs image must be compressed with zlib (there is a flag to use it). Then you reflash the image and your free rootfs space doubles or more. The subsequent times you restore your rootfs with backupmenu, zlib compression will be retained, unless you reflash the stock kernel or blank in any other way the rootfs.

Refer to the first message of the backumenu thread, and to the messages #571 to #579.

But then. if you have somewhat more than 30 megs, you're fine.

hm. Were you actually able to make a bootable image? Last I heard, you could make an image with zlib turned on, but it wasn't flashable with the Nokia flasher..?

@Robbiethe1st: you didn't read my subsequent messages, obviously
As you stated in your first post of the backupmenu thread, not all versions of mtd-utils make working images. To prepare a working zlib-compressed image I had to use the own mtd-utils of maemo5 on my n900 device.
That image worked perfectly when flashed, without making the device slower (which I feared), and more than doubled free space.

The only thing which gave me problems was on-device untarring of the tarred rootfs archive - my device stalled and thrashed optfs (where I was expanding the archive). I used my ubuntu box to untar rootfs in a directory under optfs, with my n900 connected through usb in backupmenu (option w).

I guess not, or I ended up forgetting. Hm, if it works, I'll see about adding it, then.
Oh, and for anyone who's missing something, This is the original topic.

Hi. Can I just check if this works to avoid continually losing space?
1) backup current N900 using backupmenu.
2) flash rootfs & optfs using images released by Nokia (current=PR1.3)
3) restoring backups using backupmenu from 1).

Will one only lose space once in this case?

Thanks & best regards.