From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for December 2009
Date: Mon, 11 Jan 2010 17:26:50 -0500 [thread overview]
Message-ID: <20100111222649.GA21308@infradead.org> (raw)
December finally saw the long awaited release of Linux 2.6.32, which for
XFS is mostly a bug fix release, with the major changes being various
improvement to the sync path, including working around the expectation
from the grub boot loader where metadata is supposed to be after a sync()
system call. Together with a refactoring of the inode allocator this
gives a nice diffstat for this kernel release:
46 files changed, 767 insertions(+), 1048 deletions(-)
In the meantime development for the 2.6.33 has been going strong. The
new event tracing code that allows to observe the inner workings of XFS
in production systems has finally been merged, with another patch to
reduce the size of the tracing code by using new upstream kernel features
posted for review. Also a large patch series has been posted which
changes per-AG data to be looked up by a radix tree instead of the
existing array. This works around possible deadlocks and user after
free issues during growfs, and prepares for removing a global (shared)
lock from the free space allocators. In addition to that a wide range
of fixes has been posted and applied.
Work on the userspace packages has been just as busy. In mkfs.xfs the
lazy superblock counter feature has now been enabled by default for the
upcoming xfsprogs 3.1.0 release, which will require kernel 2.6.22 for
the default mkfs invocation. Also for mkfs.xfs as patch was posted
to correct the automatic detection of 4 kilobyte sector drivers which
are expected to show up in large quantities the real work soon. The
norepair mode in xfs_repair has been enhanced with additional freespace
btree correction checks from xfs_db and is now identical to xfs_check in
filesystem consistency checking coverage. A temporary file permission
problems has been fixed in xfs_fsr, and the libhandle library has been
fixed to better deal with symbolic links. In xfs_io a few commands
that were added years ago have finally been wired up to actually be
usable. And last but not least xfsdump saw a fix to the time stamp
handling in the backup format and some usability and documentation
improvements to xfsinvutil.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2010-01-11 22:25 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=20100111222649.GA21308@infradead.org \
--to=hch@infradead.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