Oh man!
Why didn't You start this thread a few days earlier? :)
I fiddled around with that since last week and came to almost the same solution (on my own after long long heavy trials).
Here are some remarks:
I started also with ext3,then ext2 bs=4096, then 2048
but this was not ideal
du told me 4GB used and du --apparent-size said 2.5GB, so still 1.5GB lost
then I decided to use FAT (.maps is originally n a FAT drive and we do not need any rights) using a block size of 512
now du says 2.6G and du --apparent-size says 2.7G, so almost nothing lost
I had heavy problems with dd. My device always rebooted when making such heavy file transactions. Do not know why, but found using truncate helped me out (but still I had sudden reboots).
Yes, FAT does not support sparse files, a shame, right?
For the automatic start, this is absolutely perfect.
At first I also wanted to use rcS-late.
But I started using start on MOUNTS_OK, but this was triggered three times.
then switched to ke-recv, but also herein we do need some time delay, see
Code:
description "An upstart event file for Crash Reporter"
author "Eero Tamminen"
start on started ke-recv
stop on starting shutdown
pre-start script
# mmc(s) should be mounted after ke-recv has started, but currently
# started notification seems to be emitted before it's actually ready.
# this is a temporary workaround, we should fix this in ke-recv or c-r
# properly.
# sleep 4
sleep 30
end script
So, these are my 2 cents.
But nevertheless, thank You. ;)
