Bug 1257251
Summary: | Existing Logical volumes deleted after resize of LUN | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] oVirt | Reporter: | info | ||||||
Component: | vdsm | Assignee: | Fred Rolland <frolland> | ||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Gil Klein <gklein> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 3.5 | CC: | amureini, bazulay, bugs, dfediuck, ecohen, gklein, info, lsurette, mgoldboi, ovirt-bugs, rbalakri, tnisan, ycui, yeylon | ||||||
Target Milestone: | m1 | ||||||||
Target Release: | 3.6.0 | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | storage | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2015-09-20 12:26:57 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
info
2015-08-26 15:06:27 UTC
Created attachment 1069649 [details]
vdsm-Logfile ovirt0
Created attachment 1069650 [details]
vdsm-Logfile ovirt1
Hi, Changing storage from outside the VDSM is not supported. I suggest to restart the VDSM on both hosts and see if it solves the issue. Also , you can run pvscan --cache and see in lvs output if you see your logical volume. Please update with your findings. Note that in 3.6 refresh LUN size will be supported via APIs. http://www.ovirt.org/Features/LUN_Resize Restarting VDSM didnt help, because the existing volume is overwritten by the new one. No chance to recover the deleted volume. As you sad its not possible to resize the Lun in version 3.5? As workaround i add an additional LUN to get more space and waiting for 3.6 Unfortunately after the lun has been destroyed there's nothing we can do. This will be fixed in 3.6 as part of bug 609689. |