Hi Laszlo,
Thanks for all the hard work you've been putting in. I have two questions:
1) If the filesystem is crashing, doesn't it seem like we should fix
the filesystem instead of making a new file format?
2) You mentioned that fsck takes an hour for you. I'm having trouble
reproducing that. It always takes less than a minute for me. Here is
what I'm doing, let me know if I'm testing it incorrectly:
a) tangogps & find /media/mmcblk0p5/Maps | wc -l
b) Download maps (+4 levels) in tangogps (just to further stress it)
c) While that is running, I remove all power sources, causing a crash
d) At reboot, the filesystem is automatically recovered (I'm using
ext3 journaling)
e) I force a fsck and check how long it takes, like so:
umount /media/mmcblk0p5
time e2fsck -f /dev/mmcblk0p5
For me, it's always 42 seconds.
--Ben
P.S. Did you try that clock speed suggestion from BillK?
On Tue, Jun 30, 2009 at 5:05 AM, Laszlo
KREKACS<laszlo.krekacs.list at gmail.com> wrote:
> Noone experienced whole filesystem crash because of *that* many open
> file descriptors?
>> It would be really strange. ITs really simple to test it:
> While using tangogps/omgps remove the battery.
>> Almost 90% percent and the whole filesystem crashes
> (the tiles are no more availables)
>> You can test it, with: find /home/root/Maps -name *.png |wc -l
>> I bet it will hang.
>>> So I request the following feature:
> Instead of having 75000 file for 118MB, compress the
> tiles into reasonable 1MB files. So 118 files in total in place of
> 75000 files.
>> Anyone agree?
>> _______________________________________________
> Openmoko community mailing list
>community at lists.openmoko.org>http://lists.openmoko.org/mailman/listinfo/community>