| Summary: | qemu still claims ENOSPAC even if enlarge the image when doing migration | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chao Yang <chayang> |
| Component: | vdsm | Assignee: | Dan Kenigsberg <danken> |
| Status: | CLOSED NOTABUG | QA Contact: | yeylon <yeylon> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1 | CC: | abaron, bazulay, bcao, iheim, juzhang, jwest, kwolf, michen, mkenneth, owasserm, srevivo, syeghiay, tburke, virt-maint, xfu, ykaul |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-04 16:24:37 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Chao Yang
2011-03-10 06:43:26 UTC
What will happen if you'll enlarge the disk again (although it is not needed)? It might be iscsi/FC limitation since at the moment the image got enalrge, the dest was already running Maybe as a temporal work around mgmt shouldn't complete live migration in case we got any storage error in between. What happens if you do a lvmscan on destination host? Coping keving to see if he has any good idea about how this should work. My guess is that the "continue" command after enlarging the disk should do "something" also on destination. (In reply to comment #4) > What happens if you do a lvmscan on destination host? > Coping keving to see if he has any good idea about how this should work. > My guess is that the "continue" command after enlarging the disk should do > "something" also on destination. Below is lvscan result on destination host. lvscan ACTIVE '/dev/vgtest1/lvtest1' [200.00 MiB] inherit ACTIVE '/dev/vgtest1/test-enospac' [17.50 GiB] inherit(In reply to comment #2) > What will happen if you'll enlarge the disk again (although it is not needed)? > It might be iscsi/FC limitation since at the moment the image got enalrge, the > dest was already running after enlarged the disk to 17.5G, it will have the same result on destination host. (qemu) c (qemu) handle_dev_input: start block I/O error in device 'drive-ide0-0-0': No space left on device (28) handle_dev_input: stop It look like an issue with the LVM caching regarding the partition size. (If you run fdisk -l <lv path> on dest the sizeis still 512M). If you run "lvmchange --refresh <LV path> " , and continue the dest vm everything run smoothly. VDSM need to add the call to lvmchange --refresh in the migration dest after lv enlargment. Was vdsm even involved in this 7-month-old bug? which version? may I see the vdsm.log? Vdsm had a glitch of not calling lvmchange --refresh few months ago, but it was promptly fixed. Please reopen the bug if it reproduces by modern Vdsm version. |