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

[Xen-users] [Fwd: Re: FW: Lost images..]

Reposting to the list instead of list-owner (Stephan, please take care
of your To/CC headers)

-------- Forwarded Message --------
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
To: Stephan Viljoen <steph@xxxxxxxxx>
Cc: xen-users-request@xxxxxxxxxxxxxxxxxxxx
Subject: Re: FW: [Xen-users] Lost images..
Date: Thu, 26 Jun 2014 17:11:35 +0100

On Thu, 2014-06-26 at 17:53 +0200, Stephan Viljoen wrote:

> I've attached it as a txt file , I hope this is ok ?

Based on these:
/local/domain/0/backend/vbd/4/51712/physical-device = "fc:0"   (n0,r4)
/local/domain/0/backend/vbd/4/51728/physical-device = "fc:1"   (n0,r4)
/local/domain/0/backend/vbd/22/51712/physical-device = "fc:3"   (n0,r)
/local/domain/0/backend/vbd/38/51712/physical-device = "fc:2"   (n0,r)

I would say that dom4 is using devices maj:min 252:0 and 252:1, dom22 is
using 252:3 and dom38 is using 252:2.

Based on other things in your xenstore output I think 252:N is a blktap2
block device. Perhaps look for them under /dev/xen/blktap-2.

You should also have a tapdisk process for each of those disks, in which
case you could also try applying the /proc/PID/fd trick to them.


Xen-users mailing list



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