An update to my last mail, having restarted the file system servers
and all hosts in the resource pool, I now get the following when
attempting to copy the VDI for the vm in question :
There was an SR backend failure.
status: non-zero exit
stdout:
stderr: Traceback (most recent call last):
File "/opt/xensource/sm/NFSSR", line 253, in ?
SRCommand.run(NFSSR, DRIVER_INFO)
File "/opt/xensource/sm/SRCommand.py", line 246, in run
ret = cmd.run(sr)
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
caching_params)
File "/opt/xensource/sm/blktap2.py", line 1280, in activate
if self._activate_locked(sr_uuid, vdi_uuid, caching_params):
File "/opt/xensource/sm/blktap2.py", line 29, in wrapper
ret = op(self, *args)
File "/opt/xensource/sm/blktap2.py", line 1312, in
_activate_locked
dev_path = self._activate(sr_uuid, vdi_uuid, caching_params)
File "/opt/xensource/sm/blktap2.py", line 1332, in _activate
dev_path = self._tap_activate(phy_path, vdi_type, sr_uuid)
File "/opt/xensource/sm/blktap2.py", line 1135, in _tap_activate
VDI._tap_type(vdi_type))
File "/opt/xensource/sm/blktap2.py", line 711, in launch_on_tap
raise TapdiskFailed(cls.Arg(_type, path), ctl)
blktap2.TapdiskFailed:
Tapdisk(vhd:/var/run/sr-mount/0554f47c-1a12-9bd1-ea9b-d2b68984f0ed/b1dda4b8-574d-458f-83de-586e7e5e2921.vhd):
['/usr/sbin/tap-ctl', 'open', '-p', '14429', '-m', '1', '-a',
'vhd:/var/run/sr-mount/0554f47c-1a12-9bd1-ea9b-d2b68984f0ed/b1dda4b8-574d-458f-83de-586e7e5e2921.vhd']
failed: status=22, pid=14431, errmsg=
I'm pretty sure the vdi IS corrupt, but I'm not sure what utils are
available to help me repair/diagnose/query it??
I've ran the td-utils query commands direct from the shell, and I
get similar results to above error code 22 with no further info.
I've tried looking for a list of tap-disk error codes to help me
diagnose, to no avail.
Any body fancy having a stab at this?
Kind regards,
Ciaran.
On 09/09/11 13:47, David Markey wrote:
I bet your VHD is corrupt.
Can you give a bit more SMlog context, i.e. 10 lines above
and below?
Can you give dmesg output also.
On 9 September 2011 06:32, Grant McWilliams <grantmasterflash@xxxxxxxxx>
wrote:
On Mon, Sep 5, 2011 at 9:04 AM,
Ciaran Kendellen <ciaran@xxxxxxxxxxxxxxx>
wrote:
Hello there.
I had cause to force shutdown a vm recently and on
attempting to restart it I get :
Error code: SR_BACKEND_FAILURE_65
Error parameters: , Failed to load VDI [opterr=Failed
load VDI information /var/run/sr-mount/0554f47c-1a12-9bd1-ea9b-d2b68984f0ed/e82a1032-5a0c-4ff7-96cf-1f62f32938db.vhd]
The VDI is on a shared NFS repository, other vm's came
back up no problem.
Any ideas what to try anyone?
Thanks in advance,
Ciaran.
___
NFS is sideways. Start at the low layers on the host with
the NFS share and make sure everything is good there first.
For instance if you have more than one NFS mount or you
change the mount, or it doesn't mount up etc. you will get
these errors. I got this when I had an SR connected and I
shut down NFS, renamed the export and started it back up.
The SR sat there twitching until I realised what I did.
Grant McWilliams
http://grantmcwilliams.com/
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home