Innodb and xfs unclean shutdown

[Evil one]

Hey, while looking at xfs compared to other file systems i found this quote from a mailing list:

Unfortunately, XFS has a critical flaw (err, sorry, I mean
feature, if you ask the XFS devs) that makes it unsuitable for general
purpose File system. Unlike all other filesystem candidates, the meta
data is not written to disk in an ordered fashion. In the case of an
unclean shutdown, XFS will pad the difference with Null byte characters.
For example, lets say you are writing a 1kb file. 500 bytes got
flushed to disk before the system was interrupted, but the journal was
already updated with the 1kb filesize. When you reboot, you'll have a
1kb file, containing 500 bytes of data and 500 bytes of null. For the
love of all that is holy, *never* use XFS to hold something like an FTP
mirror. Most mirror scripts check file datestamp and filesize, but will
not be able to detect files trashed by XFS unless you do an md5sum check
on the whole thing.


Could this cause Innodb corruption on a sudden reboot or os crash?