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.

This bug was initially created as a copy of Bug #1769786

I am copying this bug because: 

RHEL8 needs to be consistent with RHEL7

Description of problem:

Default option for mkfs.xfs enables BLKDISCARD ioctl() on devices which support it, which can take quite a long time without providing any feedback to the user or progress, rather it looks like the command is hung. This RFE is to request an informational message printed to warn the user that mkfs might take a while when the underlying block device supports discards.  

Version-Release number of selected component (if applicable):

xfsprogs-4.5.0-20.el7
xfsprogs-5.0.0-1.el8

How reproducible:
Very

Steps to Reproduce:
1. Create a filesystem on a block device which supports discard requests


Actual results:
On very large filesystems the mkfs.xfs operation can take some time with no status or progress message indicating what mkfs is doing. 

Expected results:

Print a basic msg on creating informing the user that the requested action may need lengthy time to complete. 


Additional info:

Looks like the patch of this bug has been merged into xfsprogs-5.0.0-4.el8, right? If so, we need to add this bug into the xfsprogs erratum, and change this bug status.
https://errata.devel.redhat.com/advisory/55608

Thanks,
Zorro

Yes, my mistake, sorry.  It's even in the changelog:

commit 987337e3705b179fdad99c3c5217eb137d463de4 (HEAD -> rhel-8.3.0, origin/rhel-8.3.0)
Author: Eric Sandeen <sandeen>
Date:   Thu Jun 4 14:00:26 2020 -0400

    Make discard phase of mkfs interruptable
    
    Resolves: rhbz#1836414

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 (xfsprogs bug fix and enhancement update), 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-2020:4554