From: Alex Elder <aelder@sgi.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfsdump v3.0.5
Date: Wed, 30 Mar 2011 23:01:32 -0500 [thread overview]
Message-ID: <1301544092.2824.10.camel@doink> (raw)
Version 3.0.5 of xfsdump has been released.
A gzipped tar archive of the source code is available here:
ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsdump-3.0.5.tar.gz
The source code can be accessed via git using this URL:
git://oss.sgi.com/xfs/cmds/xfsdump.git
Below is a summary (from the doc/CHANGES file) of changes
since release 3.0.4:
xfsdump-3.0.5 (30 March 2011)
- Release tags will now be digitally signed
- Quota files will now be dumped, regardless of the maxsize
setting
- The new "-s sessid" flag allows inventory sessions to be
pruned by their session ID.
- Fixed a bug in handling long dump filenames, and dropped
(undocumented) support for encoding certain parameters
within the dump filename
- NODECHK is now off by default, meaning xfsrestore will now
support 16 times more directory entries (4 billion)
- nrh_t is now 64 bits wide, allowing xfsrestore to support
dumps with up to 4 billion directory entries
- nix_t is no longer useful, and has been eliminated
- Memory use in xfsrestore is better managed now. Segments
of nodes are now power-of-2 sized, and allocated nodes are
no longer needlessly zeroed and linked into the free list.
- Pathname resolution in xfsrestore has a number of
performance improvements
- Better checking has been implemented for compatibility
when resuming a cumulative restore
- Build system output has been cleaned up considerably
- Dead "namreg" code has been removed
- Build dependencies are now determined automatically
- Other miscellaneous build system improvements, as well bug
fixes thanks to Mike Frysinger and Arkadiusz Miśkiewicz.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2011-03-31 3:58 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=1301544092.2824.10.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