6:58 p.m.
On Jan 22, 2018 5:32 PM, "Zip" <plord(a)intricatenetworks.com> wrote:
I am having an issue where when I use the REST API to connect a snapshot
from another VM to a Backup-Appliance-VM, after the clone when I
remove the
Disk and delete the Snapshot, the disk remains in the Backup-Appliance-VM
as /dev/sdb ot /dev/vdb.
If I reboot the Bakup-Applicance-VM the disk disappears.
If I manually remove the disk by "echo 1 > /sys/block/sdb/device/delete”
the disk will disappear, but if I rescan the scsi bus, it is found and
shows up again in the VM OS, but the oVirt WebGUI does NOT show it as
connected.
-- The first part is expected - the 2nd isn't.
What are you referring to as the first and second part?
I understand why the disk is seen after it was detached (stale device), not
why it comes back after rescan, which seems to suggest it is not detached
properly.
I am also not able to attach any other disks as it complains of :
HotPlugDiskVDS failed: internal error: unable to execute QEMU command
'__com.redhat_drive_add': Duplicate ID 'drive-scsi0-0-0-2' for drive
I did see that others in the past have gotten around this issue by
rebooting the Backup-Appliance-VM and then continuing on with the next VM
backup and looping through backup-reboot-backup-reboot-etc.
Anyone have an idea on how to solve this issue and remove the hooks from
the guest OS?
Steps to reproduce this issue:
1. Create a backup appliance VM to be used for the backup script
execution
2. Currently I have the Vms set to virtio with threaded I/O enabled.
Also tried virtio_scsi with same result.
3. Using REST API – make snapshot of target VM
4. Using REST API – fetch vm metadata
5. Using REST API – attach the snapshot/disk to the Backup-Appliance-VM
6. dd the drive to backup folder
7. Using REST API – remove the disk from the Backup-Appliance-VM
8. Using REST API – delete the snapshot
9. ** Check the guest OS of the Backup-Appliance-VM and the mounted
drive from the backup above still appears and behaves as mentioned in
comments above.
— There are many details missing, including versions of everything used,
but logs would be most helpful here.
Versions for oVirt are all the most recent. This is a fresh install of the
Hosted Engine. I will just script the backup to cycle through sdb, sdc,
sdd, …. Szzzz, just seems odd that once a disk is detached and a snapshot
deleted, that the Backup_appliance-VM can still access the drive/snapshot?
Unrelated note - do NOT use /dev/sdX to enumerate them. Especially on SCSI
bus, probing is done in parallel and they may have a different name next
time. Use /dev/disk/by-id paths.
A second issue is that the above wont work when I have the Vms running on
MPIO iSCSI storage, so for testing I have moved to NFS4. Anyone have
ideas
about either issue, I’d love to hear ;)
— Same - logs would be helpful here.
I will continue to dig through this issue and will post logs if stuck. I
just wanted to know if there was anything obvious that I should be doing
differently with iSCSI vs NFS with mounting disks/snapshots.
Nope.
Y.
Zip
— Y.
Thanks
Irc.oftc.net #ovirt
zipur
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
8:12 p.m.
New subject: oVirt 4.2 - Removed disk remains in VM OS with hooks?
This message is in MIME format. Since your mail reader does not
understand
this format, some or all of this message may not be legible.
--B_3599464360_122445562
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
=20
> I am having an issue where when I use the REST API to connect a snapshot=
from
> another VM to a Backup-Appliance-VM, after the clone when I
remove the D=
isk
> and delete the Snapshot, the disk remains in the
Backup-Appliance-VM as
> /dev/sdb ot /dev/vdb.
>=20
> If I reboot the Bakup-Applicance-VM the disk disappears.
>=20
> If I manually remove the disk by "echo 1 > /sys/block/sdb/device/delete=B2=
the
> disk will disappear, but if I rescan the scsi bus, it is found
and shows=
up
> again in the VM OS, but the oVirt WebGUI does NOT show it as
connected.
=20
-- The first part is expected - the 2nd isn't.
=20
What are you referring to as the first and second part?
=8B I understand why the disk is seen after it was detached (stale device),
not why it comes back after rescan, which seems to suggest it is not
detached properly.=20
If I pass an API call to reboot, the VM reboots and the stale disks are
still connected, however if I pass an API call to shutdown, the stale disks
are removed. Is there something else that can be passed to the reboot API
call to have it disconnect whatever the shutdown does? If not, is there a
way to defer an API call as my backup VM is what is calling the API, it can=
t
call to start itself if it is off due to a shutdown call?
I dont see any errors in the logs while tailing with:
tail /var/log/ovirt-*/* -f
=20
=20
>=20
> I am also not able to attach any other disks as it complains of :
>=20
> HotPlugDiskVDS failed: internal error: unable to execute QEMU command
> '__com.redhat_drive_add': Duplicate ID 'drive-scsi0-0-0-2' for drive
>=20
> I did see that others in the past have gotten around this issue by reboo=
ting
> the Backup-Appliance-VM and then continuing on with the next VM
backup a=
nd
> looping through backup-reboot-backup-reboot-etc.
>=20
> Anyone have an idea on how to solve this issue and remove the hooks from=
the
> guest OS?
>=20
> Steps to reproduce this issue:
>=20
> 1. Create a backup appliance VM to be used for the backup script executi=
on
> 2. Currently I have the Vms set to virtio with threaded I/O
enabled. Als=
o
> tried virtio_scsi with same result.
> 3. Using REST API =AD make snapshot of target VM
> 4. Using REST API =AD fetch vm metadata
> 5. Using REST API =AD attach the snapshot/disk to the Backup-Appliance-VM
> 6. dd the drive to backup folder
> 7. Using REST API =AD remove the disk from the Backup-Appliance-VM
> 8. Using REST API =AD delete the snapshot
> 9. ** Check the guest OS of the Backup-Appliance-VM and the mounted driv=
e
> from the backup above still appears and behaves as mentioned in
comments
> above.
>=20
=20
=8B There are many details missing, including versions of everything used, =
but
logs would be most helpful here.
=20
Versions for oVirt are all the most recent. This is a fresh install of th=
e
Hosted Engine. I will just script the backup to cycle through sdb,
sdc, s=
dd,
=8A. Szzzz, just seems odd that once a disk is detached and a
snapshot dele=
ted,
that the Backup_appliance-VM can still access the drive/snapshot?
=8B Unrelated note - do NOT use /dev/sdX to enumerate them. Especially on SCS=
I
bus, probing is done in parallel and they may have a different name next
time. Use /dev/disk/by-id paths.
Each time the backup is done, it only uses the device /dev/xxY to mount the
disk image. The actual backup is being catalogued using the uuid and vmname=
.
=20
=20
> A second issue is that the above wont work when I have the Vms running o=
n
> MPIO iSCSI storage, so for testing I have moved to NFS4. Anyone
have ide=
as
> about either issue, I=B9d love to hear ;)
=20
=8B Same - logs would be helpful here.
=20
I will continue to dig through this issue and will post logs if stuck. I =
just
wanted to know if there was anything obvious that I should be doing
differently with iSCSI vs NFS with mounting disks/snapshots.
=8B Nope.=20
=8B Y.
Zip
=20
=20
Zip
=20
=8B Y.
=20
>=20
> Thanks
>=20
> Irc.oftc.net <http://Irc.oftc.net> #ovirt
> zipur
>=20
>=20
>=20
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>=20
=20
--B_3599464360_122445562
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<html><head></head><body style=3D"word-wrap: break-word;
-webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space;"><div style=3D"color: rgb(0,
0, 0=
); font-family: Calibri, sans-serif; font-size:
14px;"><div><div><br></div><=
/div></div><span id=3D"OLK_SRC_BODY_SECTION" style=3D"color:
rgb(0, 0, 0); font-=
family: Calibri, sans-serif; font-size: 14px;"><div><div><div
dir=3D"auto"><di=
v><div class=3D"gmail_extra"><div
class=3D"gmail_quote"><blockquote class=3D"quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"><div=
style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Cal=
ibri,sans-serif"><div><div><div><br></div></div></div><span
id=3D"m_-551029456=
8030381310OLK_SRC_BODY_SECTION"><div><div><div
dir=3D"ltr"><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote"><div
class=3D"quoted-text"><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div
style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-=
family:Calibri,sans-serif"><div>I am having an issue where when I use the
RE=
ST API to connect a snapshot from another VM to a Backup-Appliance-VM, after=
the clone when I remove the Disk and delete the Snapshot, the disk remains =
in the Backup-Appliance-VM as /dev/sdb ot
/dev/vdb. </div><div><br></di=
v><div>If I reboot the Bakup-Applicance-VM the disk
disappears.</div><div><b=
r></div><div>If I manually remove the disk by "echo 1 >
/sys/block/sdb/de=
vice/delete” the disk will disappear, but if I rescan the scsi bus, it=
is found and shows up again in the VM OS, but the oVirt WebGUI does NOT sho=
w it as
connected.</div></div></blockquote><div><br></div></div><div>--
The =
first part is expected - the 2nd
isn't.</div></div></div></div></div></div><=
/span><div><br></div><div>What are you referring to as the
first and second =
part? </div></div></blockquote></div></div></div><div
dir=3D"auto"><br></=
div><div dir=3D"auto">— I understand why the disk is seen
after it was d=
etached (stale device), not why it comes back after rescan, which seems to s=
uggest it is not detached
properly. </div></div></div></div></span><div=
style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14=
px;"><br></div><div style=3D"color: rgb(0, 0, 0); font-family:
Calibri, sans-s=
erif; font-size: 14px;"><br></div><div style=3D"color: rgb(0,
0, 0); font-fami=
ly: Calibri, sans-serif; font-size: 14px;">If I pass an API call to
<b>reboo=
t</b>, the VM reboots and the stale disks are still connected, however if I =
pass an API call to <b>shutdown</b>, the stale disks are removed. Is there s=
omething else that can be passed to the <b>reboot</b> API call to have it di=
sconnect whatever the <b>shutdown</b> does? If not, is there a way to defer =
an API call as my backup VM is what is calling the API, it cant call to star=
t itself if it is off due to a <b>shutdown</b> call?</div><div
style=3D"color:=
rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size:
14px;"><br></div=
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri,
sans-serif; font-siz=
e: 14px;">I dont see any errors in the logs while
tailing with:</div><div><f=
ont face=3D"Calibri,sans-serif">tail /var/log/ovirt-*/*
-f</font></div><div><b=
r></div><span id=3D"OLK_SRC_BODY_SECTION" style=3D"color:
rgb(0, 0, 0); font-fam=
ily: Calibri, sans-serif; font-size: 14px;"><div><div><div
dir=3D"auto"><div d=
ir=3D"auto"><br></div><div dir=3D"auto"><div
class=3D"gmail_extra"><div class=3D"gma=
il_quote"><blockquote class=3D"quote" style=3D"margin:0 0 0
.8ex;border-left:1px=
#ccc solid;padding-left:1ex"><div
style=3D"word-wrap:break-word;color:rgb(0,0=
,0);font-size:14px;font-family:Calibri,sans-serif"><div
class=3D"quoted-text">=
<div><br></div><span
id=3D"m_-5510294568030381310OLK_SRC_BODY_SECTION"><div><d=
iv><div dir=3D"ltr"><div class=3D"gmail_extra"><div
class=3D"gmail_quote"><div>&nb=
sp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
.8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div
style=3D"word-wrap:break-word;color:rg=
b(0,0,0);font-size:14px;font-family:Calibri,sans-serif"><div><br></div><div>=
I am also not able to attach any other disks as it complains of :</div><div>=
<br></div><div><span
class=3D"m_-5510294568030381310m_-3670774818294595794Appl=
e-tab-span" style=3D"white-space:pre-wrap"></span>HotPlugDiskVDS
failed: inter=
nal error: unable to execute QEMU command '__com.redhat_drive_add': Duplicat=
e ID 'drive-scsi0-0-0-2' for
drive</div><div><br></div><div>I did see that o=
thers in the past have gotten around this issue by rebooting the Backup-Appl=
iance-VM and then continuing on with the next VM backup and looping through =
backup-reboot-backup-reboot-et<wbr>c. </div><div><br></div><div>Anyone
=
have an idea on how to solve this issue and remove the hooks from the guest =
OS?</div><div><br></div><div>Steps to reproduce this
issue:</div><div><br></=
div><ol><li>Create a backup appliance VM to be used for the backup script
ex=
ecution</li><li>Currently I have the Vms set to virtio with threaded I/O ena=
bled. Also tried virtio_scsi with same result.</li><li>Using REST API
–=
; make snapshot of target VM</li><li>Using REST API – fetch vm
metadat=
a</li><li>Using REST API – attach the snapshot/disk to the
Backup-Appl=
iance-VM</li><li>dd the drive to backup folder</li><li>Using REST
API –=
; remove the disk from the Backup-Appliance-VM</li><li>Using REST API
–=
; delete the snapshot</li><li>** Check the guest OS of the Backup-Appliance-=
VM and the mounted drive from the backup above still appears and behaves as =
mentioned in comments
above.</li></ol><div><br></div></div></blockquote><div=
<br></div><div>— There are many details
missing, including versions o=
f everything used, but logs would be most helpful
here.</div><div> </di=
v></div></div></div></div></div></span></div><div>Versions
for oVirt are all=
the most recent. This is a fresh install of the Hosted Engine. I will just =
script the backup to cycle through sdb, sdc, sdd, …. Szzzz, just seems=
odd that once a disk is detached and a snapshot deleted, that the Backup_ap=
pliance-VM
can still access the
drive/snapshot? </div></div></blockquote></div><=
/div></div><div dir=3D"auto"><br></div><div
dir=3D"auto">— Unrelated note =
- do NOT use /dev/sdX to enumerate them. Especially on SCSI bus, probing is =
done in parallel and they may have a different name next time. Use /dev/disk=
/by-id
paths. </div></div></div></div></span><div><br></div><div>Each
t=
ime the backup is done, it only uses the device /dev/xxY to mount the disk i=
mage. The actual backup is being catalogued using the uuid and vmname.</div>=
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0);
font-family: Cal=
ibri, sans-serif; font-size: 14px;"><div><div><div
dir=3D"auto"><div dir=3D"auto=
"><br></div><div dir=3D"auto"><div
class=3D"gmail_extra"><div class=3D"gmail_quote=
"><blockquote class=3D"quote" style=3D"margin:0 0 0
.8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><div
style=3D"word-wrap:break-word;color:rgb(0,0,0);font=
-size:14px;font-family:Calibri,sans-serif"><div
class=3D"quoted-text"><div><br=
</div><div><br></div><span
id=3D"m_-5510294568030381310OLK_SRC_BODY_SECTION">=
<div><div><div dir=3D"ltr"><div
class=3D"gmail_extra"><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px
#ccc=
solid;padding-left:1ex"><div
style=3D"word-wrap:break-word;color:rgb(0,0,0);f=
ont-size:14px;font-family:Calibri,sans-serif"><div></div><div>A
second issue=
is that the above wont work when I have the Vms running on MPIO iSCSI stora=
ge, so for testing I have moved to NFS4. Anyone have ideas about either issu=
e, I’d love to hear
;)</div></div></blockquote><div><br></div><div>=
212; Same - logs would be helpful
here.</div></div></div></div></div></div><=
/span><div><br></div></div><div>I will continue to dig
through this issue an=
d will post logs if stuck. I just wanted to know if there was anything obvio=
us that I should be doing differently with iSCSI vs NFS with mounting disks/=
snapshots.</div></div></blockquote></div></div></div><div
dir=3D"auto"><br></d=
iv><div dir=3D"auto">— Nope. </div><div
dir=3D"auto">— Y.</div>=
</div></div></div></span><div><br></div><div>Zip</div><span
id=3D"OLK_SRC_BODY=
_SECTION" style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font=
-size: 14px;"><div><div><div dir=3D"auto"><div
dir=3D"auto"> </div><div dir=
=3D"auto"><br></div><div dir=3D"auto"><div
class=3D"gmail_extra"><div class=3D"gmail=
_quote"><blockquote class=3D"quote" style=3D"margin:0 0 0
.8ex;border-left:1px #=
ccc solid;padding-left:1ex"><div
style=3D"word-wrap:break-word;color:rgb(0,0,0=
);font-size:14px;font-family:Calibri,sans-serif"><div><br></div><div>Zip</di=
v><div><br></div><span
id=3D"m_-5510294568030381310OLK_SRC_BODY_SECTION"><div>=
<div><div dir=3D"ltr"><div
class=3D"gmail_extra"><div
class=3D"gmail_quote"><div>&=
#8212; Y.</div><div
class=3D"quoted-text"><div> </div><blockquote
class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><div
style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font=
-family:Calibri,sans-serif"><div><br></div><div>Thanks</div><div><br></div><=
div><a href=3D"http://Irc.oftc.net"
target=3D"_blank">Irc.oftc.net</a> #ovirt</d=
iv><div>zipur</div><div><br></div><br></div><br>
______________________________<wbr>_________________<br>
Users mailing list<br><a href=3D"mailto:Users@ovirt.org"
target=3D"_blank">User=
s(a)ovirt.org</a><br><a
href=3D"http://lists.ovirt.org/mailman/listinfo/users" r=
el=3D"noreferrer"
target=3D"_blank">http://lists.ovirt.org/mailman<wbr>/...
/users</a><br><br></blockquote></div></div><br></div></div></div></div></spa=
n></div></blockquote></div><br></div></div></div></div></div></span></body><=
/html>
--B_3599464360_122445562--
2496
days inactive
2496
days old
1 comments
2 participants
participants (2)
-
Yaniv Kaul -
Zip