Actions
Bug #13291
closedceph-disk: --zap-disk does not zap the journal device
Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When running ceph-disk prepare --zap-disk /dev/vdb /dev/vdc, only the data device /dev/vdb is zapped. It is counter intuitive and the journal device should also be zapped if present.
Updated by Owen Synge over 8 years ago
I have a fix for this, just checking for the correct pull request
Updated by Owen Synge over 8 years ago
Have a pull request here
Updated by Loïc Dachary over 8 years ago
- Tracker changed from Fix to Bug
- Subject changed from ceph-disk: --zap-disk should also zap the journal device to ceph-disk: --zap-disk does not zap the journal device
- Status changed from 12 to Won't Fix
- Regression set to No
[01.10 13:26] <loicd> ceph-disk prepare --zap-disk /dev/vdb /dev/vdc should zap /dev/vdb /dev/vdc but ceph-disk prepare --zap-disk /dev/vdb /dev/vdc1 should only zap /dev/vdb [01.10 13:27] <loicd> hum [01.10 13:27] <loicd> maybe people rely on the fact that --zap-disk only zaps the data partition [01.10 13:27] <oms101> I suspect they do [01.10 13:27] <loicd> it's confusing but if you change that behavior, scripts will start zapping unexpected things... [01.10 13:28] <loicd> oh well, that's a won't fix then I guess [01.10 13:28] <oms101> we do have zap as an explicit zap command which will zap anything [01.10 13:28] <loicd> yeah
Actions