From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Alpha2 changelog
Date: Fri, 22 Nov 2013 12:16:25 +1100 [thread overview]
Message-ID: <20131122011625.GE6502@dastard> (raw)
In-Reply-To: <528EA617.4080004@sandeen.net>
On Thu, Nov 21, 2013 at 06:32:23PM -0600, Eric Sandeen wrote:
> Here's my stab at a changelog. If you did something since 3.11, and it should be highlighted but it's not, now's your chance!
>
> xfsprogs-3.2.0-alpha2 (19 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 reports.
> - Fix potential xfs_fsr failures when running w/ selinux.
> - Update config.guess/config.sub for arm64, thanks to Colin Watson.
> - Add FALLOC_FL_COLLAPSE_RANGE support to the xfs_io fallocate command,
> thanks to Namjae Jeon.
That got reverted as the kernel parts haven't gone upstream yet.
> - 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
> transactions.
> - Print all AGI unlinked buckets in xfs_logprint.
> - Fix mkfs.xfs ENOSPC with protofile which creates a very large
> directory.
> - 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.
I think that covers most things. Thanks for doing this, Eric.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-22 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 0:32 Alpha2 changelog Eric Sandeen
2013-11-22 1:16 ` Dave Chinner [this message]
2013-11-22 9:17 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131122011625.GE6502@dastard \
--to=david@fromorbit.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox