Red Hat Bugzilla – Bug 830676
RFE: Introduce job control for storage driver.
Last modified: 2016-04-26 09:52:45 EDT
Description of problem:
When use vol-wipe to wipe a volume, and select the supported algorithms, if the volume
is large, it will take long time(except 'zero'). So during wipe the volume, if we cancel this command by Ctrl+C, this wipe process(scrub) is still running under background. Then virsh pool/vol related command will wait there until the process finished.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. wipe the image with an algorithm(nnsa/dod/bsi/gutmann, or random)
#virsh vol-wipe --pool default $image_name --algorithm nnsa
2. cancel this command by Ctrl+C
3. check the wipe process
# ps -ef|grep scrub
root 3716 3573 29 16:11 ? 00:00:06 /usr/bin/scrub -f -p nnsa /var/lib/libvirt/images/rhel6u2.img
3. check the volumes in default pool
#virsh vol-list default
The scrub process still running after cancel vol-wipe command.
The scrub process should also be killed.
More generically, we need a way to track that there is a long-running virStorageVol* command running, and be able to get status updates on its progress. For example, this argues that the virDomainGetJobInfo() API needs to be copied, and we need virStorageVolGetJobInfo().
(In reply to comment #1)
> More generically, we need a way to track that there is a long-running
> virStorageVol* command running, and be able to get status updates on its
> progress. For example, this argues that the virDomainGetJobInfo() API needs
> to be copied, and we need virStorageVolGetJobInfo().
Agreed, I recall someone raised similiar problem in upstream before.
*** This bug has been marked as a duplicate of bug 581698 ***