Bug 1475780 - [RFE] - Set "blkdiscard" as the default zero method
[RFE] - Set "blkdiscard" as the default zero method
Status: NEW
Product: vdsm
Classification: oVirt
Component: RFEs (Show other bugs)
4.18.15
Unspecified Unspecified
low Severity medium (vote)
: ovirt-4.2.0
: ---
Assigned To: Idan Shaby
Raz Tamir
: FutureFeature, Performance
Depends On: 1367806 1327886
Blocks: wipe_disk_using_blkdiscard 1314382
  Show dependency treegraph
 
Reported: 2017-07-27 06:40 EDT by Idan Shaby
Modified: 2017-09-19 03:59 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1367806
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.2?
ratamir: testing_plan_complete-
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

  None (edit)
Comment 1 Yaniv Kaul 2017-07-30 04:49:07 EDT
I think this is 'blkdiscard --zero' option here.
When we support just 'blkdiscard' (if the storage promises to return zeros on discarded blocks), it's a different option, no?
Comment 2 Idan Shaby 2017-07-30 05:09:09 EDT
Yes, but since we're talking about the config value "zero_method" (see Bug 1367806), the option name is "blkdiscard".

I will open a new BZ to track the second RFE you implied to, i.e when the user removes a disk with an intention to zero and discard it, and the underlying storage support discard_zeroes_data, then the disk is only discarded (and not wiped).
Comment 3 Allon Mureinik 2017-09-14 11:34:52 EDT
This depends on the scale's team ability to prove this method is safe.

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