> zeroing of all open files when there is an unclean shutdown. None of those were true
That one most definitely is at least partially true. I had experienced this several times using XFS on my home Linux machine in the early 2000s. I use JFS now, but supposedly this bug/misfeature was fixed some time ago, thankfully.
Edit: indeed, the linked slides themselves back me up on this; just three slides after the one quoted by the article, we have "Null files on crash problem fixed!"
No, you misunderstand. This is related to the O_PONIES problem (http://lwn.net/Articles/351422/). The bug was software that failed to use datasync when it should have. The files weren't getting zeroed out on shutdown. The data had yet to be flushed to disk, and it wasn't required to be flushed to disk. The metadata was required to be flushed to disk. For security reasons, and unallocated inode data space has to be filled with 0's. So... data not flushed to disk? You get 0's when there is an unclean shutdown.
That one most definitely is at least partially true. I had experienced this several times using XFS on my home Linux machine in the early 2000s. I use JFS now, but supposedly this bug/misfeature was fixed some time ago, thankfully.
Edit: indeed, the linked slides themselves back me up on this; just three slides after the one quoted by the article, we have "Null files on crash problem fixed!"