[Desire Android Development] melethron:
No i know why he called it unstable. No idea why but JFS partition where broken after a shutdown. Sqlite score is good and may do more testing in future.

Yep thats possible of course. A script can be even run with an update script in a flashable zip.

Quote snipped to answer step by step:

...What????? He asked if i can make script to make all the

manual steps automatically

. My script does that thats why i said he should use that one......

What???? .... i protested against FAT from the beginning and for a reason. It is unjournaled and the loopfile may not be synced because it isn't unmounted (even if the loopfile is unmounted). Every modern filesystem uses metadata journaling at least. Why did windows go for NTFS, why did linux make ext3/4 default, why did ibm create JFS ...? Do you really think that all those professional programmers don't have a reason for that. Files can be lost without full file journaling but with metadata unjournaled the

complete

FS can corrupt.

Come on... do you really intepret that sentence as shouting. Why would i shout "unjournaled" in the middle of a sentence? I mean what would that sound like. Make a test and listen what that sounds like:

I wont make a a regular zip for an (now shout) UNJOURNALED (speak normal) device.

That sounds funny IMO and not aggressive :D. I think it is obvious that i wanted to make that word bold. If you look at other posts from me you see that i use capitals rather often if im to lazy to mark the word an make it bold (check this for example: http://xdaforums.com/showpost.php?p=10513848&postcount=381 ... do you think i shout PARTITIONAME there? or FAR? or HATE. ... well hate maybe ;) .

Sibere lets not start something childish like that. If you interpreted that as shouting then im sorry (but i dont think you

really

did).

I never said that i inhabit the universal truth and i think showed clearly that i have no problem with learning lessons. I have no problem with saying im wrong instead im happy if i learn something new. I study philosophy and im really in "hegel's dialectic". A Hegelian knows how the process of learning works. Thesis - antithesis and all thos stuff ... but back to topic ^^.

But still some similarities to raid because of multiple channels. Thats why i use deadline scheduler instead of cfq ;) .

I read them (link).

Thats not true. Specifications don't include the way the controller works and the nand. The specifications is about busspeed, pins, controller channel count etc... Get some infos on the new nand chips from toshiba. Quite some development in the last year.

Quoting the sandisc specs (pdf page 6): "►Up to 2-GB of data storage"

These specs are comptible to SD-specs Quote:

SanDisk SD cards are fully compatible with the SD Card Physical Layer System

Specification, Version 1.10. This specification is available from the SD Card Association.

But these aren't the specs of SD-cards itself. What you think why a 32gb microsd can be read with a sd-card reader by only using an adapter? Because the specs only include stuff like bus-speed (up to 50mhz) pins and how the lba is accessed.

Then explain me why the different block allocating in btrfs ssd_spread option has a negative effect on ssd's (search phoronix for the benches) and also about the missing speed improvement from nilfs on a microsd (placing different files in the same directory close to each other doesn't matter on sd-cards so a log structure would help because the block allocation has not to be optimized for contiguous filestructure and would simply attach the files on empty space... this means it would not only write a 256kb block but continously to empty space without moving to a different block ... at least as long as the filesystem is "fresh").

I simply don't get how the lba is provided by the controller and according to this "http://lwn.net/Articles/353411/" the same applies for all those filesystems devs out there that want to improve ssd performance. So if you have a solution for that then tell the btrfs devs so they can improve the ssd option.....

If you write a contiguous 256kb file on the lba it doesnt necessary write to one 256kb nand block. Again if this would be the case then nilfs and btrfs with ssd option would speed things up heavy (well and it does on rather old usb sticks or sd-cards ... but so many newer test showed that things where worse). Using a logstructured filesystem was exactly my intention to manage a contignous write on the lba blocks .... and it was a fail .... and now you wanna explain me to optimize the fs by writing contignous to the blocks .... its like you missed all those filesystem discussions and tests .... Is your next idea to come up with using nilfs ?

Apart from that large files don't really matter anyway. The difference between app2sd and data2sd are that small sqlite db files from /data/data are on sd. Thats what produces the lags and thats why i use reiserfs now (tail option to store small files directly in the B+ tree).