
While Ext4 was originally merged in 2.6.19, it was marked as a development filesystem. It has been a long time coming but as planned, Ext4dev has been
renamed to Ext4 in 2.6.28 to indicate its level of maturity and paving the way for production level deployments. Ext4 filesystem developer Ted Tso also endorsed Btrfs as a multi-vendor, next generation filesystem and along with the interest from Andrew Morton, Btrfs is planned to be merged before 2.6.29 is released. It will follow a similar development process to Ext4 and be initially marked as development only.
Member since:
2005-07-24
"""
The sad thing is, traditionally, all silent corruption is detected by the hardware, not the filesystem. Design principle: "who has the relevant information? The filesystem has.
"""
In what way does the hardware not have the relevant information? A CRC, of adequate length (CRC-32?), upon each sector is well within the capability of the hardware. The hardware already does one, possibly of inadequate length. What is sad is that we are seriously considering moving this thing which should be incumbent upon the hardware, back to the software, at significant processing cost.
I am not convinced that silent corruption is a real problem. Maybe it is, and maybe it isn't. But if it is, it should be fixed at the proper layer. And that layer is the hardware, and not the filesystem. And if you *still* insist that the proper layer is somewhere in the OS, why not the block layer?
Edited 2008-10-20 15:59 UTC