Ext4 Data Losses Explained, Worked Around

ddfall writes "H-Online has a follow-up on the Ext4 file system — Last week's news about data loss with the Linux Ext4 file system is explained and new solutions have been provided by Ted Ts'o to allow Ext4 to behave more like Ext3."

LOL: Bug Report

[Em Emalb]

User: My data, it's gone!
EXT4:"Ext4 developer Ted Ts'o stresses in his answer to the bug report that Ext4 behaves precisely as demanded by the POSIX standard for file operations."

Solution: WORKS AS DESIGNED

Show some respect!

[LotsOfPhil]

...new solutions have been provided by Ted Ts'o to...

That's General Ts'o to you!

Re:the workaround is bad design

[jd]

But... those of us who learned the Ancient And Most Wise ways always triple-sync. We also sacrifice Peeps and use red food colouring in voodoo ceremonies (hey, it really is blood, so it should work) to keep the hardware from failing.

On next week's Slashdot, there will be a brief tutorial on the right way to burn a Windows CD at the stake, and how to align the standing stones known as RAM Chips to points of astronomical significance.

Re:I sit just me?

[Em Emalb]

Nope, not just you, I sit also.

Re:Show some respect!

[TheGratefulNet]

"what's a matter, colonel? CHICKEN?"

sorry.

voting

[Skapare]

So is this why we can't have voting (where correctness is paramount over performance) systems developed on Linux?

Re:LOL: Bug Report

[ijakings]

Microsoft Patent

Re:Those who fail to learn the lessons of history.

[noidentity]

Delayed block allocation allows the filing system to optimise its write processes, but at the price that the metadata of a newly created file will display a size of 0 bytes and occupy no data blocks until the delayed allocation takes place. [...] And now my question: Why did the Ext4 developers make the same mistakes Reiser and XFS both made (and later corrected) years ago? [...] Those who fail to learn the lessons of [change] history are doomed to repeat it.

They tried to, but history was just a 0-byte file.