[Galaxy S I9000 General] pikachu01:
It does apparently. You should read more about journaling and its usage model. Having almost no knowledge on it and commenting about it is putting a bad light on your credibility :)

Write caches and disk caches is used when the bottleneck between CPU and disks are too great, and data is buffered onto an intermediary storage before writing it. The same goes for reading. This is for performance reasons.

http://en.wikipedia.org/wiki/Disk_buffer

Tell me in which area does disk buffers are used for data integrity.

And they don't stay in the buffer for years. Unless its a new technology that isn't documented publicly.

And yes disks using the RAID system is mainly for data integrity/security. Disks have battery packs as a failsafe. When there's a sudden power outage, some remaining data can still be in disk buffer waiting to be written. It solves the problem of having the remaining data still get written successfully as data in the disk buffer is not journaled.

Read more about journaling :)

Journaling actually creates a metadata of a transaction that can be replayed in the event of a power loss.

Hence, even if the data is still in RAM, or the data is loss, for e.g.:

CPU requests a write of Data address 0xA from 0xB.

CPU creates a metadata journal of the request of writing data from address 0xB to 0xA.

Transaction is happening ....

Still happening ...

BOOM, power loss

Some data is still in RAM - It's gone.

CPU resumes from power loss. Sees a metadata journal not committed.

CPU attempts to replay the journal.

CPU resumes the transaction from address 0xB to 0xA - corruption is not likely.

Umm, I would assume that all modern CPU architecture would access the RAM the same way no matter journaling or non-journaling is applied.

Open files = files in memory, no?

Lack of knowledge in the area?

No worries - here's a summary of the basic computer architecture to get you up to scratch:

http://johnmeister.com/old-cs/470/VonNeumann.pdf

LOL, joke of the day.

Unless Android is built by aliens from outer space that forked Linux and went back to the future to create a non-cache Linux architecture, you're plain wrong. Man, you really need to read more before actually commenting. Your lack of knowledge really pains my hands typing all these when they're already in Wikipedia.

Type this in your android terminal emulator:

sysctl -a | grep vm

Google each of them and tell me what they are actually doing :)

Oh wait, here's a link:

http://www.kernel.org/doc/Documentation/sysctl/vm.txt

Btw, dirty data means uncommitted data (for the uninformed :P)

Ramdisks is actually a way of cutting up your RAM out of a block and using it as a logical disk. It's a faster disk, but you lose that block of RAM. It is sometimes used as addons to the journaling (or non-journaling) filesystems. They're mostly used as swap space in Linux.

Wow. Just wow.

http://www.linux-magazine.com/Online/News/Linus-Torvalds-Upset-over-Ext3-and-Ext4

I could say the same thing about myself too actually :) Go ahead and read those articles and then try to say something to me with facts. You can spout out anything you want, but please please PLEASE PLEASE PLEASE copy paste some hard facts or at least an internet article that says what you've just typed. I'll be satisfied and withdraw myself from XDA, or do something to get myself banned :)

If not, please refrain from commenting about something that you yourself clearly do not have any idea about :)

The term bootloop is not to say that your boot partitions caused the problem. The term bootloop is when your data partition is corrupted and when the system tries to mount it, it gets an error that the mount is not clean and doesn't want to mount it. Android system sees this and doesn't know how to react, thus - bootloop.

OR

Data partition is corruptied and the Linux system tries to read something (maybe something from /data/dalvik-cache/ in which the files inside it was corrupted), it then fails to launch the dex files and the system keeps reloading the UI, it seems like a faster reboot, but it bootloops - so called (I've seen quite a lot of cases of this)

And yes, many have gotten this before from messing around with no journaling filesystems.

Heck, even corruption on Windows filesystems sometimes lead to a point where you can't boot Windows. Why isn't it the same for non-journaling filesystems where corruption happened?