New XFS Programs Update Supports New XFS On-Disk Format
After a year of development, xfsprogs 3.2.0 has been released as the latest version of the user-space program and other components for the XFS file-system. The big addition to xfsprogs 3.2.0 is supporting a new on-disk format.
The xfsprogs 3.2.0 supports creating the version 5 on-disk format for the XFS file-system. This new XFS format has "significant reliability enhancements" with meta-data CRCs, object back owner references, and better crash recovery reliability. With the upcoming Linux 3.15 kernel this XFS v5 on-disk format is now considered stable / ready for production workloads and lost its experimental marking just with 3.15-rc5.
Besides supporting the new XFS on-disk format, there's been hundreds of other commits over the past year from over a dozen developers. Other changes including making XFS repair have significantly improved multi-threaded scalability, XFS_db improvements, XFS_io supports a lot of new kernel features, and libxfs is closer to the kernel code where it's derived.
More details on the XFS 3.2.0 tooling update can be found via the release announcement sent out this morning by Dave Chinner.
The xfsprogs 3.2.0 supports creating the version 5 on-disk format for the XFS file-system. This new XFS format has "significant reliability enhancements" with meta-data CRCs, object back owner references, and better crash recovery reliability. With the upcoming Linux 3.15 kernel this XFS v5 on-disk format is now considered stable / ready for production workloads and lost its experimental marking just with 3.15-rc5.
Besides supporting the new XFS on-disk format, there's been hundreds of other commits over the past year from over a dozen developers. Other changes including making XFS repair have significantly improved multi-threaded scalability, XFS_db improvements, XFS_io supports a lot of new kernel features, and libxfs is closer to the kernel code where it's derived.
More details on the XFS 3.2.0 tooling update can be found via the release announcement sent out this morning by Dave Chinner.
23 Comments