Bug 1422158 - [Docs][RFE][VMM] Document New Enable Discard checkbox for virtual disks
Summary: [Docs][RFE][VMM] Document New Enable Discard checkbox for virtual disks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ovirt-4.1.1-1
: ---
Assignee: Julie
QA Contact: Megan Lewis
URL:
Whiteboard:
Depends On: RHEV_pass_discard_from_guest
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-14 15:46 UTC by Emma Heftman
Modified: 2019-05-07 13:14 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-19 22:29:11 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Emma Heftman 2017-02-14 15:46:20 UTC
Previously, discard commands (UNMAP SCSI commands) that were sent from the guest were ignored by qemu and were not passed on to the underlying storage. This meant that storage that was no longer in use could not be freed up. In this release, it is now possible to pass on discard commands to the underlying storage. A new property called Enable Discard was added to the Virtual Disk window. When selected, and if all the restrictions are met, discard commands that are sent from the guest will not be ignored by qemu and will be passed on to the underlying storage. The reported unused blocks in the underlying storage thinly provisioned LUNs will be marked as free, and the reported consumed space will be reduced. 

Update virtual disk chapter

Comment 1 Lucy Bopf 2017-03-14 05:28:09 UTC
More information is available at the following location:

http://www.ovirt.org/develop/release-management/features/storage/pass-discard-from-guest-to-underlying-storage/

Comment 2 Lucy Bopf 2017-03-15 06:27:22 UTC
Assigning to Julie for review.


Note: A related feature for "discard after delete" is tracked in bug 1420186.


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