Bug 1156352 - blkdiscard progress report and interruptibility of the process
Summary: blkdiscard progress report and interruptibility of the process
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: util-linux
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks: 1172230
TreeView+ depends on / blocked
 
Reported: 2014-10-24 09:25 UTC by Federico Simoncelli
Modified: 2015-08-17 15:22 UTC (History)
3 users (show)

Fixed In Version: util-linux-2.23.2-19.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 13:18:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0501 0 normal SHIPPED_LIVE util-linux bug fix and enhancement update 2015-03-05 16:20:51 UTC

Description Federico Simoncelli 2014-10-24 09:25:42 UTC
Description of problem:
At the moment blkdiscard is issuing a single ioctl with the entire chunk of block device to be discarded. This operation may take a long time (depending on the discard granularity of the device) and it is impossible to determine what is the status of completion and interrupt the process.

Managing software (such as oVirt) would like to use blkdiscard (instead of re-writing a similar tool) but they need progress report and the ability to interrupt the process if needed.


Version-Release number of selected component (if applicable):
util-linux-2.23.2-18.el7

Steps to Reproduce:
1. blkdiscard -v /dev/large/device


Actual results:
No progress report, process is uninterruptible until the entire device is discarded.

Expected results:
Progress should be reported and it should be possible to interrupt the process.


Additional info:
An initial work on the fix can be found here:

https://github.com/simon3z/util-linux/commit/4e5e19aa6788061eae52804622237dfe7d0c863f

Comment 7 errata-xmlrpc 2015-03-05 13:18:49 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-2015-0501.html


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