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.
Bug 1162819 - mkfs.gfs2: print message about BLKDISCARD ioctl taking a long time
Summary: mkfs.gfs2: print message about BLKDISCARD ioctl taking a long time
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gfs2-utils
Version: 7.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Paul Evans
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1271674
Blocks: 1111393 1497636
TreeView+ depends on / blocked
 
Reported: 2014-11-11 18:47 UTC by Nate Straz
Modified: 2017-10-02 09:59 UTC (History)
5 users (show)

Fixed In Version: gfs2-utils-3.1.9-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 06:29:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch - Print message about BLKDISCARD ioctl (1.33 KB, patch)
2015-10-19 13:36 UTC, Paul Evans 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2438 0 normal SHIPPED_LIVE gfs2-utils bug fix and enhancement update 2016-11-03 14:01:57 UTC

Description Nate Straz 2014-11-11 18:47:05 UTC 
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:
Comment 4 Paul Evans 2015-10-19 13:36:22 UTC 
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.
Comment 5 Mike McCune 2016-03-28 23:16:15 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 6 Andrew Price 2016-06-07 15:31:59 UTC 
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=498444
Comment 8 Justin Payne 2016-07-26 17:13:40 UTC 
Verified in gfs2-utils-3.1.9-3.el7:

[root@south-16 ~]# rpm -q gfs2-utils
gfs2-utils-3.1.9-3.el7.x86_64
[root@south-16 ~]# mkfs.gfs2 -t lock_nolock -p test:mygfs2 /dev/sdb1
Invalid lock protocol: test:mygfs2
[root@south-16 ~]# mkfs.gfs2 -p lock_nolock -t test:mygfs2 /dev/sdb1
It appears to contain an existing filesystem (gfs2)
This will destroy any data on /dev/sdb1
Are you sure you want to proceed? [y/n]y
Discarding device contents (may take a while on large devices): Done
Adding journals: Done 
Building resource groups: Done       
Creating quota file: Done
Writing superblock and syncing: Done
Device:                    /dev/sdb1
Block size:                4096
Device size:               1791.57 GB (469649399 blocks)
Filesystem size:           1791.57 GB (469649398 blocks)
Journals:                  1
Resource groups:           7167
Locking protocol:          "lock_nolock"
Lock table:                "test:mygfs2"
UUID:                      5d589a85-391d-8471-4939-a3838893905e
Comment 10 errata-xmlrpc 2016-11-04 06:29:41 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.