Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1563170 - original resize2fs command hang on RHEL7.4 [rhel-7.5.z]
original resize2fs command hang on RHEL7.4 [rhel-7.5.z]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: e2fsprogs (Show other bugs)
7.4
x86_64 Linux
urgent Severity medium
: rc
: ---
Assigned To: Lukáš Czerner
Boyang Xue
Marek Suchanek
: Patch, Reproducer, ZStream
Depends On: 1553004
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-03 06:34 EDT by Oneata Mircea Teodor
Modified: 2018-05-14 12:12 EDT (History)
8 users (show)

See Also:
Fixed In Version: e2fsprogs-1.42.9-12.el7_5
Doc Type: If docs needed, set a value
Doc Text:
Previously, the resize2fs utility became unresponsive when resizing a file system that contained more than 16TB of data. This happened due to a 32-bit integer overflow in resize2fs. With this update, the overflow has been fixed, and the described problem no longer occurs.
Story Points: ---
Clone Of: 1553004
Environment:
Last Closed: 2018-05-14 12:12:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1398 None None None 2018-05-14 12:12 EDT

  None (edit)
Description Oneata Mircea Teodor 2018-04-03 06:34:38 EDT
This bug has been copied from bug #1553004 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 12 Marek Suchanek 2018-04-27 09:58:19 EDT
Thanks, I'm changing that part to 32.
Comment 15 errata-xmlrpc 2018-05-14 12:12:05 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1398

Note You need to log in before you can comment on or make changes to this bug.