From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] New gfs2-utils-3.1.1 release
Date: Wed, 23 Feb 2011 13:08:07 -0500 (EST) [thread overview]
Message-ID: <1628649254.151580.1298484487360.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <2038341380.151565.1298484449813.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
Hi,
I just wanted to let everyone know that I just did a new build of gfs2-utils.
The new source tarball can be downloaded here:
https://fedorahosted.org/releases/g/f/gfs2-utils/gfs2-utils-3.1.1.tar.gz
To report bugs or issues:
https://bugzilla.redhat.com/
Regards,
Bob Peterson
Red Hat File Systems
Changes since 3.1.0:
Bob Peterson (14):
gfs2_edit savemeta doesn't save all leaf blocks for large dirs
fsck.gfs2: segfault in pass1b
gfs2_edit: fix segfault in set_bitmap when block is in rgrp
gfs2_edit: fix careless compiler warning
gfs2_edit: Fix error message on blockalloc when outside bitmap
gfs2_edit: add -d option for printing journal details
gfs2_edit: has problems printing gfs1 journals
gfs2_edit: print large block numbers better
gfs2_edit: handle corrupt file systems better
fsck.gfs2: can't repair rgrps resulting from gfs_grow->gfs2_convert
fsck.gfs2: reports master/root dinodes as unused and fixes the bitmap
gfs2-utils: minor corrections to README.build
GFS2: mkfs.gfs2 segfaults with 18.55TB and -b512
mkfs.gfs2 should support discard request generation
Ben Marzinski (1):
gfs2_grow: fix growing on full filesystems
Dave Teigland (1):
gfs_controld: remove oom_adj
Steve Whitehouse (5):
libgfs2: Move gfs2_query into gfs2_convert
libgfs2: Remove unused function get_sysfs_uinit()
libgfs2: Remove calls to gettext from libgfs2
strings: Clean up strings
tune: Clean up and make closer to tune2fs
parent reply other threads:[~2011-02-23 18:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2038341380.151565.1298484449813.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>]
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=1628649254.151580.1298484487360.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com \
--to=rpeterso@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).