Journals only protect metadata, not data. Google don't care how long fsck takes (they never run it), but they *do* care about I/O rates. So they don't want to use a journal.
Posted Mar 24, 2009 18:19 UTC (Tue) by tialaramex (subscriber, #21167)
[Link]
The data=journal mode protected data, didn't it?
But yes, some people (and Google are apparently enough people to count) want the best possible FS features minus journalling.
Also fsck is probably /faster/ in ext4 than ext2, so Google would be wise to choose ext4 w/o journalling over ext2 even if they did care about fsck performance. Sparse inode structures iirc were a particularly big fsck win.
The 2.6.29 kernel is out
Posted Mar 24, 2009 19:59 UTC (Tue) by cortana (subscriber, #24596)
[Link]
The data=journal mode protected data, didn't it?
Apparantly not. I think you want the 'sync' mount option in this case.
The 2.6.29 kernel is out
Posted Mar 24, 2009 20:45 UTC (Tue) by tialaramex (subscriber, #21167)
[Link]
Ted's talking about ext4 there, not ext3. Combining delayed allocation with data journalling clearly doesn't make much sense. But point taken.