From: Ben Myers <bpm@sgi.com>
To: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: XFS status update for May 2013
Date: Wed, 26 Jun 2013 14:16:35 -0500 [thread overview]
Message-ID: <20130626191635.GT32736@sgi.com> (raw)
May saw the merge of the XFS development tree for Linux 3.10 into
mainline as well as a number of fixes after the initial merge.
Linux 3.10 will be an exciting release for XFS as this release includes
an experimental feature, CRC protection for on-disk metadata structures.
In order to create a CRC enabled filesystem, build the crc-dev branch of
xfsprogs located at git://oss.sgi.com/xfs/cmds/xfsprogs.git and mkfs.
We also saw the release of xfsprogs-3.1.11 and xfsdump-3.1.3. xfsprogs
includes a numerous fixes for xfs_repair, xfs_metadump, mkfs, and
xfs_db. xfsdump has fixes for a backward compatability problem with
dumps created with 3.1.2, and a fix for a segfault in xfsrestore.
Other work that was posted in May includes a series of fixes for log
space validation, a revision of a patchset to allow project and group
quotas to be used simultaneously, and a number of new tests for
xfstests.
reply other threads:[~2013-06-26 19:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130626191635.GT32736@sgi.com \
--to=bpm@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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