Comment 0 for bug 1102004
Revision history for this message
| Attila Fazekas (afazekas) wrote Optional storage clear on delete | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
The storage clear on delete has significant I/O impact
https:/
On large volume deletion you had to wait too many before you can use your storage space again.
On systems with limited I/O performance , like in the OpenStack gate (test) system it has significant impact on performance and reliability (test timing).
In private clouds where you consider all data in the volume group as your data, you do not need to sanitize the storage.
Please make this method call optional, even with a lot of warning.
NOTE:
The device-mapper thin provisioning layer is able to sanitize chunks just on the first access, in this case you do not need to "manually" sanitize on delete. It requires at least 3.2 Linux kernel version, and you can use it with the dmsetup command.
Newer lvm2 packages support it by the lvcreate command too.