Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 872530 - (wipe_disk_using_blkdiscard) [RFE][Tracker] - Wipe volumes using "blkdiscard" instead of "dd"
[RFE][Tracker] - Wipe volumes using "blkdiscard" instead of "dd"
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs (Show other bugs)
3.1.0
All All
high Severity high
: ovirt-4.2.2
: ---
Assigned To: Idan Shaby
Kevin Alon Goldblatt
: FutureFeature, Tracking
: 1014324 (view as bug list)
Depends On: 1367806 1475780
Blocks: CEECIR_RHV43_proposed 1314382
  Show dependency tree / graph
 
Reported: 2012-11-02 07:05 EDT by Andrew Cathrow
Modified: 2018-05-16 13:00 EDT (History)
17 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
The default zeroing method has been changed from "dd" to "blkdiscard", which allows storage offloading, if supported by the storage array, and consumes much less network bandwidth. The zeroing method can be reverted by adding "zero_method = dd" to /etc/vdsm/vdsm.conf.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-05-15 13:35:57 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
sherold: Triaged+
ratamir: testing_plan_complete-

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 88026 master MERGED config: change default zero method to blkdiscard 2018-03-19 04:11 EDT
oVirt gerrit 89153 ovirt-4.2 MERGED config: change default zero method to blkdiscard 2018-03-20 03:29 EDT
Red Hat Product Errata RHEA-2018:1488 None None None 2018-05-15 13:37 EDT

  None (edit)
Description Andrew Cathrow 2012-11-02 07:05:43 EDT 
oVirt includes an option to wipe a disk after it is deleted to securely erase the disk image.

To perform this we do a simple overwrite, however we may need to perform a more secure erasure for security and compliance reasons. (eg. PCI compliance etc)


We should mirror the work performed by the libvirt team in which they provide a number of algorithms to use when wiping an image.

http://www.redhat.com/archives/libvir-list/2012-January/msg00070.html
Comment 6 Andrew Cathrow 2013-10-10 11:32:11 EDT 
*** Bug 1014324 has been marked as a duplicate of this bug. ***
Comment 10 wiley crider 2014-04-22 13:26:27 EDT 
The customer requested a status as this is dependent on a VDI implementation.
Comment 24 Yaniv Kaul 2016-04-26 10:23:18 EDT 
*** Bug 981626 has been marked as a duplicate of this bug. ***
Comment 25 Allon Mureinik 2016-06-16 04:31:51 EDT 
This is an RFE targeted for 4.1.
Idan is working on it, but the work is being done on the code, not on bugzilla, so there aren't too many updates here.

Reducing priority to HIGH to avoid nagging emails from nagging whines.
Comment 26 Yaniv Lavi 2017-07-31 04:26:26 EDT 
Moving to MODIFIED as BZ #1367806 upstream is already being tested.
Comment 27 Idan Shaby 2017-07-31 04:30:32 EDT 
Yaniv, please note that Bug 1367806 only adds blkdiscard as an option to wipe volumes, but it is not the default option.
BZ 1475780 is responsible for making it the default wiping method.
Comment 29 Allon Mureinik 2017-08-06 02:10:37 EDT 
Yaniv - please see comment 27 (was missing a needinfo, probably). I think this should be moved back to ASSIGNED.
Comment 30 Allon Mureinik 2017-09-14 08:50:39 EDT 
ATM, this is an available via optional configuration. Setting it to the default is pending the scale's team help on verifying it's usefulness/safety.
Comment 34 Kevin Alon Goldblatt 2018-03-27 04:54:32 EDT 
https://bugzilla.redhat.com/show_bug.cgi?id=1475780 - VERIFIED

Used the XtremIO storage provider:

XtremIO Storage Management Application
© Copyright 2009-2016 XtremIO. All rights reserved.

Version: 4.2.1 build 7

Moving to VERIFIED
Comment 37 errata-xmlrpc 2018-05-15 13:35:57 EDT 
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://access.redhat.com/errata/RHEA-2018:1488
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.