[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] XCP 1.1 SR_BACKEND_FAILURE_46 The VDI is not available [opterr=VDI already attached RW] issue

  • To: xen-api@xxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Fri, 18 Jan 2013 12:28:04 +0400
  • Delivery-date: Fri, 18 Jan 2013 08:28:17 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>

XCP 1.1?

There is few cases for that message.

1) Some hosts hangs and was forcefully rebooted
2) Some VM crashed no no lock has been removed on normal host (bug).

You can

1) use /opt/xensource/sm/resetvdis.py
2) Manually remove lock from VDI in state.db (eek, extremely low level hacking with horrible possible consequences) 3) Check every host in pool for hanged tapdisks (simply check all /proc/PID/fd for every tapdisk to see if someone still locking vdi).

Anyway, that message is just notice that lock is preventing to do bad stuff. If can be false alarm, or may be last thing on Earth saving your VMs from complete trashing.

17.01.2013 19:59, Jan MartinÅ ÐÐÑÐÑ:

I have a problem with VDI already attached RW in the "adding tag" in blktap2. This issue is on all hosts in pool with attached lvmoiscsi SR.

Is there any solution to this problem?


[32484] 2013-01-17 14:59:44.200883 vdi_activate {'sr_uuid': 'e33281eb-ba4c-3829-9b61-7c64764dff9c', 'subtask_of': 'OpaqueRef:78dd7c48-383b-253c-9c2d-a60edcb9e2e1', 'vdi_ref': 'OpaqueRef:9e3252f6-403b-7045-2147-401beeafc8ca', 'vdi_on_boot': 'persist', 'args': ['true'], 'vdi_location': 'ff54dd4f-5ad3-4cf2-814f-9abd12b1045e', 'host_ref': 'OpaqueRef:a8aeb980-a584-bf7f-d9dd-377f27d030f7', 'session_ref': 'OpaqueRef:5b8af71e-3432-0ce6-3ed4-4fe2fe0197a7', 'device_config': {'target': '', 'chappassword_secret': 'b47a23a5-4939-d613-8641-51c740b8dd87', 'chapuser': 'cloud1', 'targetIQN': 'iqn.2011-04.cz.vshosting:storage1.cloud1', 'SRmaster': 'true', 'device': '/dev/disk/by-id/scsi-26c756e3020636239', 'SCSIid': '26c756e3020636239', 'targetlist': ''}, 'command': 'vdi_activate', 'vdi_allow_caching': 'false', 'sr_ref': 'OpaqueRef:9fc8a54a-dd45-4313-f783-7883b3335604', 'vdi_uuid': 'ff54dd4f-5ad3-4cf2-814f-9abd12b1045e'}
[32484] 2013-01-17 14:59:44.201233 blktap2.activate
[32484] 2013-01-17 14:59:44.201476 lock: acquired /var/lock/sm/ff54dd4f-5ad3-4cf2-814f-9abd12b1045e/vdi [32484] 2013-01-17 14:59:44.201567 Adding tag to: ff54dd4f-5ad3-4cf2-814f-9abd12b1045e [32484] 2013-01-17 14:59:44.238928 ***** BLKTAP2:<function _activate_locked at 0xb6fbc064>: EXCEPTION util.SMException, VDI ff54dd4f-5ad3-4cf2-814f-9abd12b1045e already attached RW
File "/opt/xensource/sm/blktap2.py", line 32, in wrapper
ret = op(self, *args)
File "/opt/xensource/sm/blktap2.py", line 1297, in _activate_locked
if not self._add_tag(vdi_uuid):
File "/opt/xensource/sm/blktap2.py", line 1230, in _add_tag
raise util.SMException("VDI %s already attached RW" % vdi_uuid)

[32484] 2013-01-17 14:59:44.272130 Raising exception [46, The VDI is not available [opterr=VDI ff54dd4f-5ad3-4cf2-814f-9abd12b1045e already attached RW]] [32484] 2013-01-17 14:59:44.272325 lock: released /var/lock/sm/ff54dd4f-5ad3-4cf2-814f-9abd12b1045e/vdi [32484] 2013-01-17 14:59:44.272847 ***** vdi_activate: EXCEPTION SR.SROSError, The VDI is not available [opterr=VDI ff54dd4f-5ad3-4cf2-814f-9abd12b1045e already attached RW]
File "/opt/xensource/sm/SRCommand.py", line 94, in run
return self._run_locked(sr)
File "/opt/xensource/sm/SRCommand.py", line 131, in _run_locked
return self._run(sr, target)
File "/opt/xensource/sm/SRCommand.py", line 183, in _run
File "/opt/xensource/sm/blktap2.py", line 1283, in activate
if self._activate_locked(sr_uuid, vdi_uuid, caching_params):
File "/opt/xensource/sm/blktap2.py", line 40, in wrapper
raise xs_errors.XenError(excType, opterr=msg)
File "/opt/xensource/sm/xs_errors.py", line 49, in __init__
raise SR.SROSError(errorcode, errormessage)

Xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.