From: Alex Elder <aelder@sgi.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfsprogs v3.1.6
Date: Fri, 14 Oct 2011 09:29:28 -0500 [thread overview]
Message-ID: <1318602568.3827.16.camel@doink> (raw)
Version 3.1.6 of xfsprogs has been released.
The source code can be accessed via git using this URL:
git://oss.sgi.com/xfs/cmds/xfsprogs.git
A gzipped-tar archive of the source code is available here:
ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsprogs-3.1.6.tar.gz
The development tree for this code (not available at
the moment) is normally published here as well:
git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
Below is a summary (from the doc/CHANGES file) of changes
since release 3.1.5:
xfsprogs-3.1.6 (14 October 2011)
- Re-synch of the header and libxfs files with the kernel
code as of Linux 2.6.37, including reviving xfs_repair
radix tree code.
- Fix a xfs_repair phase 4 hang, thanks to Ajeet Yadav.
- Subcommand names within various programs are no longer
translated/localized, thanks to Arkadiusz Mi?kiewicz.
- Build system fixes, thanks to Ted Ts'o.
- Updates to teh xfs_info(8)/xfs_growfs(8) man page, thanks
to Roman Ovchinnikov.
- xfs_quota "df" no longer reports values twice what they
should have been for project quotas.
- mkfs.xfs now requires that sub-options are non-empty
strings; thanks to Chris Pearson for reporting.
- Better handling of short reads in libxfs.
- xfs_quota now prints "N/A" rather than a large number for
the quota file inode number for disabled quota types.
- Bogus (unrelated) mount point entries no longer cause
xfs_growfs, xfs_quota, and xfs_io to quit early.
- xfs_repair no longer fails when the sector size of an
underlying device is larger than the sector size in a
hosted filesystem image.
- Various other internal improvements, including refactoring
and eliminating more build warnings.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2011-10-14 14:29 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=1318602568.3827.16.camel@doink \
--to=aelder@sgi.com \
--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