- Issued:
- 2013-09-30
- Updated:
- 2013-09-30
RHBA-2013:1339 - gfs2-utils bug fix update
Synopsis
gfs2-utils bug fix update
Type/Severity
Bug Fix Advisory (none)
Topic
Updated gfs2-utils packages that fix several bugs are now available for Red Hat Enterprise Linux 5.
Description
The gfs2-utils packages contain a number of utilities for creating, checking, modifying, and correcting any inconsistencies in GFS2 file systems.
This update fixes the following bugs:
-
Previously, a bug in the fsck.gfs2 utility caused files to be placed in the /lost+found/ directory, and these files could not be deleted in some circumstances. As a result, the fsck.gfs2 utility in Red Hat Enterprise Linux 6.4 was better able to repair GFS2 file system damage than in 5.9 or earlier versions. This update corrects these issues by including several fixes for the bugs from a newer version of the fsck.gfs2 utility, and Red Hat Enterprise Linux version 5.10 is able to fix GFS2 file systems as well as in version 6.4. (BZ#877150)
-
Prior to this update, the manual pages included in the gfs2-utils package were incorrectly installed with permissions set to 0755. This was not necessary, because manual pages do not contain executable data. This update fixes the problem by updating the package to install these manual pages with permissions set to 0644, which is similar to other manual pages. (BZ#883864)
-
The gfs2_convert utility allows the user to convert a file system from GFS to GFS2. Previously, this utility did not properly convert files and directories with certain metadata characteristics. As a consequence, running the fsck.gfs2 utility after such a conversion produced a number of errors. This update fixes the gfs2_convert tool so that it properly handles those file and directory metadata characteristics. As a result, the fsck.gfs2 utility no longer reports errors when run after a conversion. (BZ#887374)
-
Prior to this update, if one of gfs2_tool, gfs2_quota, gfs2_grow, or gfs2_jadd was killed unexpectedly, a temporary GFS2 metadata mount point used by those tools could be left mounted. The mount point was also not registered in /etc/mtab and so the "umount -a -t gfs2" command would not unmount it. This mount point could prevent systems from rebooting properly, and cause the kernel to panic in cases where it was manually unmounted after the normal GFS2 mount point. This update fixes the problem by creating an mtab entry for the temporary mount point and unmounting it before exiting when signals are received. (BZ#994643)
Users of gfs2-utils are advised to upgrade to these updated packages, which fix these bugs.
Solution
Before applying this update, make sure all previously-released errata relevant to your system have been applied.
This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258
Affected Products
| Product | Version | Arch |
|---|---|---|
| Red Hat Enterprise Linux for Power, big endian | 5 | ppc |
| Red Hat Enterprise Linux Workstation | 5 | x86_64 |
| Red Hat Enterprise Linux Workstation | 5 | i386 |
| Red Hat Enterprise Linux Server | 5 | x86_64 |
| Red Hat Enterprise Linux Server | 5 | ia64 |
| Red Hat Enterprise Linux Server | 5 | i386 |
| Red Hat Enterprise Linux Server from RHUI | 5 | x86_64 |
| Red Hat Enterprise Linux Server from RHUI | 5 | i386 |
| Red Hat Enterprise Linux Desktop | 5 | x86_64 |
| Red Hat Enterprise Linux Desktop | 5 | i386 |
Updated Packages
- gfs2-utils-0.1.62-39.el5.x86_64.rpm
- gfs2-utils-debuginfo-0.1.62-39.el5.ppc.rpm
- gfs2-utils-debuginfo-0.1.62-39.el5.x86_64.rpm
- gfs2-utils-debuginfo-0.1.62-39.el5.i386.rpm
- gfs2-utils-0.1.62-39.el5.i386.rpm
- gfs2-utils-0.1.62-39.el5.ia64.rpm
- gfs2-utils-debuginfo-0.1.62-39.el5.ia64.rpm
- gfs2-utils-0.1.62-39.el5.src.rpm
- gfs2-utils-0.1.62-39.el5.ppc.rpm
Fixes
(none)
CVEs
(none)
References
(none)
Additional information
- The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.