From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: XFS status update for November 2011
Date: Mon, 12 Dec 2011 09:49:38 -0500 [thread overview]
Message-ID: <20111212144938.GA25014@infradead.org> (raw)
November saw stabilization of the Linux 3.2 release candidates, including
a few fixes for XFS. In addition a lot of bug fixes were backported to
the 3.0 long term stable and 3.1-stable releases for users not on
bleeding edge kernels.
At the same time development for Linux 3.3 went on at a fast pace, although
no pages were merged into the development tree yet. The highlights are:
- further versions of the patches to log all file size updates instead of
relying the the flaky VM writeback code for them
- an initial version of SEEK_HOLE/SEEK_DATA support
- removal of the old non-delaylog logging code, and cleanups resulting
from the removal
- large updates for the quota code
Userspace development was even more busy:
Xfsprogs saw the rushed 3.1.7 release which contains Debian packaging fixes,
a polish translation update and a xfs_repair fix. In the meantime a lot of
xfs_repair fixes were posted but mostly not reviewed and commit yet.
Xfsdump grew support for using pthreads to write backup streams to multiple
tapes in parallel, and SGI_XFSDUMP_SKIP_FILE which has been deprecated in
favor of the nodump flag has finally been removed.
Xfstests saw an enormous amount of updates. The fsstress tool saw major
updates to exercise even more system calls, and found numerous bugs in
all major Linux filesystems, additional ENOSPC tests, a new test for
btrfs-specific functionality and the usual amount of bug fixes and small
cleanups. Also a series to clean up the very large filesystem testing,
including extending the support to ext4 was posted but not committed yet.
next reply other threads:[~2011-12-12 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 14:49 Christoph Hellwig [this message]
2011-12-12 14:52 ` XFS status update for November 2011 Sedat Dilek
2011-12-12 14:56 ` 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=20111212144938.GA25014@infradead.org \
--to=hch@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).