Red Hat Bugzilla – Bug 742476
Make eject fail for non-removable drives even with -f
Last modified: 2013-01-09 19:24:15 EST
Description of problem: You could eject -f non-removable drives, such as hard disks.hard disk should be removed via device_del. Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.192.el6.x86_64 guest kernel #uname -r 2.6.32-195.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.boot guest 2.(qemu) info block drive-virtio0-0-0: type=hd removable=0 file=/home/timerdevice/rhel62-guest-new.qcow2 ro=0 drv=qcow2 encrypted=0 3.(qemu) info status VM status: running (qemu) block I/O error in device 'drive-virtio0-0-0': Input/output error (5) block I/O error in device 'drive-virtio0-0-0': Input/output error (5) block I/O error in device 'drive-virtio0-0-0': Input/output error (5) Actual results: After step3,disk is rejected. Expected results: should not be eject successful Additional info:
http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-September/msg00677.html According to our test results. with this patch fix this issue.add this issue into tracker bug(bz742458)
It might be fixed with the above series in 6.2 but I'll move it to 6.3 just in case
Moving back to 6.2, because I want all the prerequisites for tracker bug 742458 there.
Verified with qemu-kvm-0.12.1.2-2.199.el6,the steps are as same as comment0 Results: (qemu) eject -f drive-virtio-disk0 Device 'drive-virtio-disk0' is not removable
Moving to ON_QA because Errata Tool did not do it
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: Monitor command eject -f worked even for non-removable drives Consequence: Unwise eject -f of non-removable drive made the drive unusable for guest (looks like bad hardware failure) Fix: Refuse to eject non-removable drive Result: User needs to be more creative to screw up his guest.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2011-1531.html