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

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Thu, 2014-06-26 at 18:15 +0200, Stephan Viljoen wrote:
> Thanks a mill Ian , much appreciated.
> 
> Just to be clear on "/proc/PID/fd trick" ... I just basically copy the block 
> back into a file right?

TBH I've never done it so I'm not sure. I think so though (maybe dd not
cp). Perhaps google a bit first though just in case.

> 
> 
> 
> -----Original Message-----
> From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx] 
> Sent: Thursday, June 26, 2014 6:12 PM
> To: Stephan Viljoen
> Cc: xen-users-request@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: FW: [Xen-users] Lost images..
> 
> 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.
> 
> Ian.
> 
> 



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users