feature request: quick disk erase
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | MAAS |
Wishlist
|
Blake Rouse | ||
Bug Description
Please consider adding a "quick erase" feature, such as writing 0s to the first and last N number of blocks.
The current disk erase feature can take many hours to complete and release the node, which is not realistically usable in test automation where many deploys are exercised every day.
I think this feature would also have value for normal users who want to ensure that the partition table (specifically GPT) is adequately ruined, but aren't concerned about a full or secure wipe.
As an example: we run into particular issues with ceph, where a previous deployment can affect a new deployment, because GPT survives on /dev/sdb.
Thank you!
| Christian Reis (kiko) wrote : | #1 |
| Ryan Beisner (1chb1n) wrote : | #2 |
Linking for reference with regard to gpt:
http://
http://
| Changed in maas: | |
| milestone: | none → 1.9.0 |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| Christian Reis (kiko) wrote : | #3 |
See also bug 1507724
| Blake Rouse (blake-rouse) wrote : | #4 |
This is already being done in MAAS 1.9. We a node is deployed all disks get there superblock wiped and the start of every partition also gets wiped, just in case its the exact same partition offset as a previous deployment.
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| tags: | added: storage |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |


How long does hdparm --secure-erase take? On an SSD I believe it just swaps out the encryption key, so it should be instantaneous.