cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2-utils 3.1.5 Released
Date: Mon, 12 Nov 2012 20:37:36 +0000	[thread overview]
Message-ID: <50A15E10.8030009@redhat.com> (raw)

Hi,

gfs2-utils 3.1.5 has been released. This version features bug fixes and 
performance enhancements for fsck.gfs2 in particular, better handling of 
symlinks in mkfs.gfs2, a small block manipulation language to aid future 
testing, a gfs2_lockcapture script which replaces gfs2_lockgather, and 
various other minor enhancements and bug fixes.

The mount.gfs2 helper utility has been removed as it is no longer 
required to mount gfs2 file systems. gfs2_tool and gfs2_quota have also 
been removed. Users of gfs2_quota should now use the generic quota 
utilities and users of gfs2_tool should now use tunegfs2, gfs2 mount 
options and the generic dmsetup and chattr/lsattr tools.

See below for a full list of changes. The source tarball is available from:

   https://fedorahosted.org/released/gfs2-utils/gfs2-utils-3.1.5.tar.gz

To report bugs or issues, please file them against the gfs2-utils 
component of Fedora (rawhide) at:

 
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=gfs2-utils&version=rawhide

Regards,

Andy Price
Red Hat File Systems


Changes since 3.1.4:

Andrew Price (29):
       gfs2_utils: Improve error messages
       fsck.gfs2: Fix handling of eattr indirect blocks
       libgfs2: Remove gfs_get_leaf_nr
       libgfs2: Clean up some warnings
       gfs2-utils: Remove references to unlinked file tag
       gfs2_edit: Fix find_mtype and support gfs1 structures
       gfs2_edit: Clean up some magic offsets
       libgfs2: Use flags for versions in metadata description
       mkfs.gfs2: Check for symlinks before reporting device contents
       gfs2-utils: Remove obsolete tools
       gfs2-utils: Make building gfs_controld optional
       gfs2-utils: Only build group/ when gfs_controld is enabled
       gfs2-utils: Remove unused exported functions
       mkfs.gfs2: Avoid a rename race when checking file contents
       fsck.gfs2: Fix buffer overflow in get_lockproto_table
       libgfs2: Remove exit calls from inode_read and inode_get
       libgfs2: Remove exit call from __gfs_inode_get
       gfs2_edit: Some comment cleanups
       mkfs.gfs2: Check locktable more strictly for valid chars
       libgfs2: Add a gfs2 block query language
       libgfs2: Move valid_block into fsck.gfs2
       libgfs2: gfs2_get_bitmap performance enhancements
       fsck.gfs2: Fix build failure
       gfs2-utils: build: Avoid using the kernel versions of kernel headers
       libgfs2: Add a small testing language UI
       gfs2-utils: Update .gitignore
       gfs2-utils: Remove gfs2_lockgather
       gfs2-utils: Rename lockgather directory to lockcapture
       gfs2-utils: Remove remaining references to gfs2_lockgather

Bob Peterson (8):
       gfs2_edit savemeta: Get rid of "slow" mode
       gfs2_edit savemeta: report save statistics more often
       gfs2_edit savemeta: fix block range checking
       gfs2_edit restoremeta: sync changes on a regular basis RHEL6
       gfs_controld: fix ignore_nolock for mounted nolock fs
       fsck.gfs2: soften the messages when reclaiming freemeta blocks
       fsck.gfs2: Check for formal inode number mismatch
       GFS2: Fix a compiler warning in pass2's check_dentry

Shane Bradley (1):
       gfs2-utils: Added a new script called gfs2_lockcapture that will 
capture lockdump data.

Steven Whitehouse (3):
       libgfs2: libgfs2.h: Add gfs_block_tag structure, and some more 
flag symbols
       mount.gfs2: Remove obsolete tool
       libgfs2: Add pointer restriction flags



                 reply	other threads:[~2012-11-12 20:37 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=50A15E10.8030009@redhat.com \
    --to=anprice@redhat.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).