[Top] [All Lists]

[ANNOUNCE] xfsprogs: v3.2.0 released!

To: xfs@xxxxxxxxxxx
Subject: [ANNOUNCE] xfsprogs: v3.2.0 released!
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 16 May 2014 15:56:50 +1000
Delivered-to: xfs@xxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)

It is my pleasure to announce the release of v3.2.0 of the xfsprogs
package. This release has been a long time in the making with a lot
of effort from many people:

        - just over a year since v3.1.11 was released
        - 323 commits
        - 17 contributors
        - 10 code reviewers
        - 232 files changed
        - +29549/-24432 lines of code

The major feature that this release brings is support for the
version 5 on-disk format. This new format provides significant
reliability enhancements such as metadata CRCs, object back owner
references and improved crash recovery reliability.

The next kernel to be released (v3.15) will also be the first kernel
to support this new on-disk format for production workloads: the
kernel no longer considers this new format experimental as of

There are many other enhancements:

        - xfs_repair has significantly improved multithreading
        - xfs_db now uses the common libxfs IO engine
        - xfs_db validates the metadata it reads from disk
        - xfs_io has support for a wide range of new kernel features
        - xfs_metadump has much improved obfuscation support
        - libxfs has significanty fewer differences to the kernel
          code it is derived from

The source code can be accessed via git using this URL:


A signed gzipped-tar archive of the source code is available here:


Problems, issues, questions and general discussion about the release
should be directed to the XFS mailing list (xfs@xxxxxxxxxxx).

A summary of the changes during development of this release (taken
from doc/CHANGES) is as follows:

xfsprogs-3.2.0 (16 May 2014)
        - First release with full support of CRC enabled filesystems
        - No code changes from 3.2.0-rc3

xfsprogs-3.2.0-rc3 (9 May 2014)
        - Third release candidate for full support of CRC enabled filesystems
        - Updated Debian change logs in preparation for release (Nathan Scott)
        - Build warning fixes (Nathan Scott)
        - xfs_repair prefetch fix (Eric Sandeen)
        - xfs_repair block tracking scalability fix

xfsprogs-3.2.0-rc2 (2 May 2014)
        - Second release candidate for full support of CRC enabled filesystems
        - xfs_repair has full CRC validation and repair
        - Coverity related cleanups and fixes

xfsprogs-3.2.0-rc1 (14 April 2014)
        - First release candidate for full support of CRC enabled filesystems
        - Large number of Coverity related fixes and cleanups
        - disambiguous of CRC validation errors from IO errors.
        - Improved dangerous mode handling in repair
        - repair handles garbage in zeroed areas of superblocks better
        - repair validates dirent ftype field fully
        - metadump fully supports discontiguous directory blocks
        - metadump only recalculates CRCs on metadata it obfuscates so as to
          preserve errors in the metadata where possible.
        - default log size that mkfs creates is now reverted to the same size
          as 3.1.x releases create.
        - mkfs sets the ftype on directory entries correctly during protofile
        - xfs_io support O_TMPFILE, flink, FALLOC_FL_ZERO_RANGE and
        - logprint handles split entries better

xfsprogs-3.2.0-alpha2 (25 November 2013)
        - Alpha release for the purpose of testing the CRC feature in
          kernels 3.10 and newer.
        - Enable xfs_db write support and xfs_metadump support for CRC
          enabled filesystems.
        - Add directory entry filetype support for non-CRC filesystems.
        - Remove experimental warnings for CRC filesystems.
        - Ensure all inodes created by xfs_repair have a proper d_type set.
        - Fix build on big endian machines.
        - Properly handle symlinks to devices on various tool commandlines.
        - Fix xfs_repair's dirty log detection for 4k sector logs, broken
          in Alpha1.
        - Fix a potential segfault in xfs_repair when issuing progress
        - Fix potential xfs_fsr failures when running w/ selinux.
        - Update config.guess/config.sub for arm64, thanks to Colin Watson.
        - Stop wasting memory by caching inode structures in xfs_repair -
          they are never re-used.  Thanks to Christoph Hellwig.
        - Fix several Coverity-found defects, thanks to Li Zhong.
        - Fix platform_test_xfs_fd to return false on special files which
          cannot take an xfs ioctl.
        - Sync up libxfs with kernel code.
        - Improved xfs_repair performance on large filesystems
          (always use prefetch and strided AG scanning functionality)

xfsprogs-3.2.0-alpha1 (26 September 2013)
        - Alpha release for the purpose of testing the CRC feature in
          kernels 3.10 and newer.
        - Remove all vestiges of old, unsupported version 1 directory code.
        - Add a "readdir" command to xfs_io, thanks to Brian Foster.
        - Fix potential segfault in xfs_repair when creating lost+found.
        - Zero out unused parts of on-disk superblocks during repair, to
          avoid metadata verifier failures at runtime.
        - Add directory entry type support to mkfs.xfs and xfs_db.
        - Add the icreate transaction to xfs_logprint, and fix continuation
        - Add the lseek SEEK_DATA/SEEK_HOLE support into xfs_io.
        - Print all AGI unlinked buckets in xfs_logprint.
        - Fix mkfs.xfs ENOSPC with protofile which creates a very large
        - Fix several Coverity-found defects, thanks to Li Zhong.
        - Do all file reads in xfs_fsr using O_DIRECT.
        - Sync up libxfs with kernel code.
        - Add support for concurrent group and project quota usage on CRC
          enabled filesystems.
        - Ensure mkfs creates log sizes that are always large enough for
          the configured fileystem geometry.

Dave Chinner

Attachment: signature.asc
Description: Digital signature

<Prev in Thread] Current Thread [Next in Thread>