From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for May 2009
Date: Tue, 9 Jun 2009 08:34:21 -0400 [thread overview]
Message-ID: <20090609123421.GA15623@infradead.org> (raw)
In May Linux 2.6.30 was getting close to be released, and various
important XFS fixes made it during the latest release candidates.
In the meantime some big patch series to rework the sync code and
the inode allocator have been posted for the next merge window.
On the userspace side xfsprogs and xfsdump 3.0.1 were finally released,
quickly followed by 3.0.2 releases with updated Debian packaging.
After that various small patches that were held back made it into xfsprogs.
A patch to add the xfs_reno tool which allows to move inodes around to
fit into 32 bit inode number space has been posted which is also one
central aspect of future online shrinking support.
There has been major activity on xfstests including adding generic
filesystems support to allow running tests that aren't XFS-specific on
any Linux filesystems.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2009-06-09 12:34 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=20090609123421.GA15623@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