<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<big>Hello,<br>
<br>
after adding a new vm/harddisk, the existing disk of a running
vm was overwritten.<span lang="en"><br>
I do not know why this happened , so I need your help .</span><br>
<br>
<br>
<br>
* ovirt-engine<br>
- OS: CentOS 7 <br>
- packages: <br>
ovirt-engine-sdk-python-3.5.2.1-1.el7.centos.noarch<br>
ovirt-engine-cli-3.5.0.6-1.el7.noarch<br>
ovirt-engine-lib-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-jboss-as-7.1.1-1.el7.x86_64<br>
ovirt-engine-setup-plugin-websocket-proxy-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-tools-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-restapi-3.5.3.1-1.el7.centos.noarch<br>
ovirt-image-uploader-3.5.1-1.el7.centos.noarch<br>
ovirt-host-deploy-java-1.3.1-1.el7.noarch<br>
ovirt-engine-setup-plugin-ovirt-engine-common-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-webadmin-portal-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-userportal-3.5.3.1-1.el7.centos.noarch<br>
ovirt-iso-uploader-3.5.2-1.el7.centos.noarch<br>
ovirt-engine-extensions-api-impl-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-dbscripts-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-setup-plugin-ovirt-engine-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-backend-3.5.3.1-1.el7.centos.noarch<br>
ovirt-host-deploy-1.3.1-1.el7.noarch<br>
ovirt-engine-setup-base-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-websocket-proxy-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-setup-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-3.5.3.1-1.el7.centos.noarch<br>
ovirt-engine-extension-aaa-ldap-1.0.2-1.el7.noarch<br>
ovirt-release35-005-1.noarch<br>
<br>
<br>
* 4 ovirt hosts, risn-ovirt0 to risn-ovirt3<br>
<br>
- OS: Centos 7<br>
- packages <br>
ovirt-release35-005-1.noarch<br>
vdsm-xmlrpc-4.16.20-0.el7.centos.noarch<br>
vdsm-4.16.20-0.el7.centos.x86_64<br>
vdsm-jsonrpc-4.16.20-0.el7.centos.noarch<br>
vdsm-yajsonrpc-4.16.20-0.el7.centos.noarch<br>
vdsm-cli-4.16.20-0.el7.centos.noarch<br>
vdsm-python-zombiereaper-4.16.20-0.el7.centos.noarch<br>
vdsm-python-4.16.20-0.el7.centos.noarch<br>
<br>
<br>
* 1 Storagedomain called space0.dc1 ( Data Fibre channel ) <br>
This storagedomain is attached and accessable to all ovirt hosts.<br>
<br>
Some details of the space0.dc1<br>
<br>
[root@]# multipath -ll <br>
360060e80101e2500058be22000000bb8 dm-2 HITACHI ,DF600F <br>
size=550G features='0' hwhandler='0' wp=rw<br>
|-+- policy='service-time 0' prio=1 status=active<br>
| |- 2:0:1:1 sdh 8:112 active ready running<br>
| `- 3:0:1:1 sdt 65:48 active ready running<br>
`-+- policy='service-time 0' prio=0 status=enabled<br>
|- 2:0:0:1 sdd 8:48 active ready running<br>
`- 3:0:0:1 sdp 8:240 active ready running<br>
<br>
--- Volume group ---<br>
VG Name bb5b6729-c654-4ebe-ba96-8ddc96154595<br>
System ID <br>
Format lvm2<br>
Metadata Areas 2<br>
Metadata Sequence No 82<br>
VG Access read/write<br>
VG Status resizable<br>
MAX LV 0<br>
Cur LV 14<br>
Open LV 3<br>
Max PV 0<br>
Cur PV 1<br>
Act PV 1<br>
VG Size 549.62 GiB<br>
PE Size 128.00 MiB<br>
Total PE 4397<br>
Alloc PE / Size 1401 / 175.12 GiB<br>
Free PE / Size 2996 / 374.50 GiB<br>
VG UUID cE1V2A-ghtI-PldK-UNKH-d83q-tKg0-BdTZdy<br>
<br>
* vm elvira (exisiting server)<br>
OS: Linux<br>
Disk size: 30GB<br>
harddisk: space0.dc1<br>
Image id: c11f91e2-ebec-41ee-b3b4-ceb013a58743<br>
<br>
* vm betriebsserver (new one)<br>
OS: Windows<br>
disk size: 300GB<br>
harddisk: space0.dc1<br>
image id: e19c6c85-cfa6-4350-9a01-48d007f6f934<br>
<br>
<br>
I did the following steps:<br>
<br>
* extended the storagedomain to 550GB on our storage system.<br>
<br>
I executed the following commands on every ovirt hosts:<br>
- for letter in {a..z} ; do echo 1 >
/sys/block/sd${letter}/device/rescan; done<br>
- multipathd resize map 360060e80101e2500058be22000000bb8<br>
- pvresize /dev/mapper/360060e80101e2500058be22000000bb8<br>
<br>
* After that i created a new server called "betriebsserver"<br>
<br>
* added a new harddisk with 300GB and attached it to the
betriebsserver<br>
<br>
* installed the Windows OS.<br>
<br>
* At 13:39 i rebooted another vm called "elvira", but the server
wont coming up, because the harddisk is missing.<br>
<br>
Logfile of risn-ovirt3 where elvira was running.<br>
Thread-449591::ERROR::2015-08-25
13:39:12,908::task::866::Storage.TaskManager.Task::(_setError)
Task=`4b84a935-276e-441c-8c0b-3ddb809ce853`::Unexpected error<br>
Thread-449591::ERROR::2015-08-25
13:39:12,911::dispatcher::76::Storage.Dispatcher::(wrapper)
{'status': {'message': "Volume does not exist:
('c11f91e2-ebec-41ee-b3b4-ceb013a58743',)", 'code': 201}}<br>
<br>
The server was unable to boot due to missing harddisk.<br>
I tried it on every ovirt hosts, but no success.<br>
<br>
<br>
* i checked if the lvm exists on the risn-ovirt3<br>
[root@risn-ovirt3 vdsm]# find / -name
"*c11f91e2-ebec-41ee-b3b4-ceb013a58743*"<br>
/dev/bb5b6729-c654-4ebe-ba96-8ddc96154595/c11f91e2-ebec-41ee-b3b4-ceb013a58743<br>
/run/vdsm/storage/bb5b6729-c654-4ebe-ba96-8ddc96154595/d0299b2b-5c82-45d3-b45f-f23c7d89ed5f/c11f91e2-ebec-41ee-b3b4-ceb013a58743<br>
/run/udev/links/\x2fbb5b6729-c654-4ebe-ba96-8ddc96154595\x2fc11f91e2-ebec-41ee-b3b4-ceb013a58743<br>
<br>
* For testing purposes i copied the disk
/dev/bb5b6729-c654-4ebe-ba96-8ddc96154595/c11f91e2-ebec-41ee-b3b4-ceb013a58743
to a new testserver ( dd and netcat )<br>
When i started this testserver the server booted into windows OS
instead of linux.<br>
So the harddisk from the betriebsserver has overwritten the the
harddisk from elvira.<br>
<br>
* Output from risn-ovirt3:<br>
The id c11f91e2--ebec--41ee--b3b4--ceb013a58743 is used by elvira
but the partitions are the same as from the betriebsserver.<br>
<br>
Disk
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-c11f91e2--ebec--41ee--b3b4--ceb013a58743:
32.2 GB, 32212254720 bytes, 62914560 sectors<br>
Units = sectors of 1 * 512 = 512 bytes<br>
Sector size (logical/physical): 512 bytes / 512 bytes<br>
I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
Disk label type: dos<br>
Disk identifier: 0xbb481efc<br>
<br>
Device Boot Start End Blocks Id System<br>
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-c11f91e2--ebec--41ee--b3b4--ceb013a58743p1
2048 514047 256000 7 HPFS/NTFS/exFAT<br>
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-c11f91e2--ebec--41ee--b3b4--ceb013a58743p2
514048 718847 102400 6 FAT16<br>
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-c11f91e2--ebec--41ee--b3b4--ceb013a58743p3
718848 980991 131072 6 FAT16<br>
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-c11f91e2--ebec--41ee--b3b4--ceb013a58743p4
* 980992 629143551 314081280 7 HPFS/NTFS/exFAT<br>
<br>
Disk
/dev/mapper/9c015850--06ed--4e14--9b36--e5b1d371b6f6-a98c818c--03d6--44ab--93b9--76991a97f37c:
32.2 GB, 32212254720 bytes, 62914560 sectors<br>
Units = sectors of 1 * 512 = 512 bytes<br>
Sector size (logical/physical): 512 bytes / 512 bytes<br>
I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
Disk label type: dos<br>
Disk identifier: 0xbb481efc<br>
<br>
<br>
* Output from risn-ovirt0 which is running vm "betriebsserver".<br>
<br>
Disk
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-e19c6c85--cfa6--4350--9a01--48d007f6f934:
322.1 GB, 322122547200 bytes, 629145600 sectors<br>
Units = sectors of 1 * 512 = 512 bytes<br>
Sector size (logical/physical): 512 bytes / 512 bytes<br>
I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
Disk label type: dos<br>
Disk identifier: 0xbb481efc<br>
<br>
Device Boot Start End Blocks Id System<br>
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-e19c6c85--cfa6--4350--9a01--48d007f6f934p1
2048 514047 256000 7 HPFS/NTFS/exFAT<br>
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-e19c6c85--cfa6--4350--9a01--48d007f6f934p2
514048 718847 102400 6 FAT16<br>
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-e19c6c85--cfa6--4350--9a01--48d007f6f934p3
718848 980991 131072 6 FAT16<br>
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-e19c6c85--cfa6--4350--9a01--48d007f6f934p4
* 980992 629143551 314081280 7 HPFS/NTFS/exFAT<br>
<br>
Disk
/dev/mapper/bb5b6729--c654--4ebe--ba96--8ddc96154595-a6def31d--9e7b--4ff4--b983--e26a495e0ce4:
2147 MB, 2147483648 bytes, 4194304 sectors<br>
Units = sectors of 1 * 512 = 512 bytes<br>
Sector size (logical/physical): 512 bytes / 512 bytes<br>
I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
Disk label type: dos<br>
Disk identifier: 0x148e5b3c<br>
<br>
<br>
Has anybody an idea why this happened?<br>
Did i make a mistake when i extended the storage size?<span
lang="en"><br>
I can also provide the logfiles.</span><br>
</big>
<pre dir="ltr" data-fulltext="" class="tw-data-text vk_txt tw-ta tw-text-medium" data-placeholder="Übersetzung" id="tw-target-text" style="text-align: left; height: 72px;"><big>
Thx in advance
regards
Bernhard
</big></pre>
<big><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</big>
</body>
</html>