Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1138346

Summary: Unable to boot a vm if the bootable disk is shared with other running vm
Product: [Retired] oVirt Reporter: Raz Tamir <ratamir>
Component: ovirt-engine-coreAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: low    
Version: 3.5CC: amureini, ecohen, gklein, iheim, michal.skrivanek, rbalakri, yeylon
Target Milestone: ---   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-02 11:03:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1084103    
Bug Blocks:    
Attachments:
Description Flags
vdsm and engine logs none

Description Raz Tamir 2014-09-04 14:32:31 UTC
Created attachment 934481 [details]
vdsm and engine logs

Description of problem:
when trying to boot a vm from a disk that is shared with another vm that is already running an error message appears in boot sequence and the boot fails with the error: "Duplicate or bad block in use!"


Version-Release number of selected component (if applicable):
ovirt-engine-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch


How reproducible:
100%

Steps to Reproduce:
setup: 2 vms with the same bootable disk
1. run one of the vms
2. after the first vm is up, run the second vm
3.

Actual results:
the second vm will fail to boot with the error: "Duplicate or bad block in use!"

Expected results:


Additional info:

Comment 1 Raz Tamir 2014-09-04 14:48:07 UTC
Update:
Probably what causing this related to bug: https://bugzilla.redhat.com/show_bug.cgi?id=1138335

Comment 2 Allon Mureinik 2014-09-11 09:48:00 UTC
Don't think there's anything intelligent to do here - if guest1 corrupts the disk guest2 has nothing to do.

Moving to the virt stakeholders in case I missed something, but from a storage perspective there's no AI here.

Comment 3 Michal Skrivanek 2014-10-30 14:57:54 UTC
there's no AI in virt either, though we really try!:-)

The only thing coming to my mind is to have a general warning when you are marking disk as shared and rw that (obviously) you have to manually take care of concurrency.

Allon, thoughts? A nice RFE?:-)

Comment 4 Allon Mureinik 2014-11-07 10:55:07 UTC
We could have something like that ("note that this disk is writable by VM1 and VM2"), but I wonder if it's worth the effort.

Comment 5 Michal Skrivanek 2014-11-07 12:31:36 UTC
will close if no one picks it up in few months... (which is likely)

Comment 6 Michal Skrivanek 2015-06-02 11:03:19 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.