Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When running mkfs.gfs2 issues the BLKDISCARD ioctl() it can sit waiting for quite a long time without providing any feedback. It looks like the command is hung doing nothing. I think mkfs.gfs2 should print a message out before it starts the ioctl to warn the user this might take a while.
Example:
100TB LUN on EMC VNX, ~1.5TB used
ioctl(3, BLKDISCARD, {0, 7fff86ee8200}) = 0 <7763.742314>
Version-Release number of selected component (if applicable):
gfs2-utils-3.1.7-1.el7.x86_64
How reproducible:
easily w/ large sparse block devices
Steps to Reproduce:
1. Create sparse LUN
2. Make a file system and use some of the space
3. mkfs.gfs2 /dev/foo
Actual results:
Expected results:
Additional info:
Created attachment 1084411[details]
Patch - Print message about BLKDISCARD ioctl
Here is a Patch posted upstream to the Master branch. It adds a warning to the user just before the BLKDISCARD ioctl begins stating that it can take a long time to complete.
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://rhn.redhat.com/errata/RHBA-2016-2438.html
Description of problem: When running mkfs.gfs2 issues the BLKDISCARD ioctl() it can sit waiting for quite a long time without providing any feedback. It looks like the command is hung doing nothing. I think mkfs.gfs2 should print a message out before it starts the ioctl to warn the user this might take a while. Example: 100TB LUN on EMC VNX, ~1.5TB used ioctl(3, BLKDISCARD, {0, 7fff86ee8200}) = 0 <7763.742314> Version-Release number of selected component (if applicable): gfs2-utils-3.1.7-1.el7.x86_64 How reproducible: easily w/ large sparse block devices Steps to Reproduce: 1. Create sparse LUN 2. Make a file system and use some of the space 3. mkfs.gfs2 /dev/foo Actual results: Expected results: Additional info: