Project

General

Profile

Actions

Bug #9232

closed

disk zap doesnt remove the dmcrypt settings on disk

Added by Tamilarasi muthamizhan over 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
ceph-disk
Target version:
-
% Done:

0%

Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Well, am really not sure how this is supposed to behave.

deployed a cluster using ceph-deploy and enabled dmcrypt on the disks when creating osds.
after I have destroyed the cluster [purge and purgedata], the disks that were dmcrypt enabled still remains the same, no change even after i zap it.

while i think zap would officially deal with the data, am not sure if zap could also clear the dmcrypt flag or something.

This makes me think, if dmcrypt is a one time setting that i can never dare to play with and the only way i can reset is by formatting the disk? doesnt sound like a good idea.

Actions #1

Updated by Sage Weil over 9 years ago

  • Priority changed from Normal to High
Actions #2

Updated by Alfredo Deza over 9 years ago

  • Status changed from New to 4

I think that `disk zap` would certainly have to clear the dmcrypt flags in the disk.

Can you make sure that it does (or doesn't) to ensure that this is really an issue?

Actions #3

Updated by Sage Weil almost 6 years ago

  • Status changed from 4 to Closed
Actions

Also available in: Atom PDF