Thank you for report, its very useful for investigation. But only one difference between v1 and v2 is ploop disk size in header (32 vs 64 bit). But I use 64 bit numbers anywhere and everything should work fine. But I suppose alignment issues which not handled in my tool.<br><br>On Friday, September 12, 2014, Roman Haefeli <<a href="mailto:reduzent@gmail.com">reduzent@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, 2014-09-12 at 11:15 +0200, Roman Haefeli wrote:<br>
> On Fri, 2014-09-12 at 10:56 +0200, Roman Haefeli wrote:<br>
> > Hi Pavel<br>
> ><br>
> > I might have some more information on the issue. It seems that only<br>
> > 'old' ploop images cannot be mounted by ploop_userspace. I actually<br>
> > don't quite know the ploop version I used for creating the 'old' ploop<br>
> > images, but I know it works well with images created with ploop v1.6.<br>
> ><br>
> > Does ploop_userspace know about older image formats?<br>
><br>
> No, it's also not the version.<br>
<br>
Yes, there are different versions... I must have checked on the wrong<br>
machine. ploop_userspace works well with images created by ploop v1.11,<br>
but not with images created by ploop v1.6.<br>
<br>
Sorry for the noise.<br>
<br>
Roman<br>
<br>
<br>
<br>
><br>
> > On Thu, 2014-08-28 at 22:53 +0400, Pavel Odintsov wrote:<br>
> > > Hello!<br>
> > ><br>
> > > No, it's not depend on kernel version. I created issue for you and<br>
> > > will try to investigate:<br>
> > > <a href="https://github.com/FastVPSEestiOu/ploop_userspace/issues/10" target="_blank">https://github.com/FastVPSEestiOu/ploop_userspace/issues/10</a> please<br>
> > > track this github issue.<br>
> > ><br>
> > > On Thu, Aug 28, 2014 at 6:12 PM, Roman Haefeli <<a href="javascript:;" onclick="_e(event, 'cvml', 'reduzent@gmail.com')">reduzent@gmail.com</a>> wrote:<br>
> > > > Some more info:<br>
> > > ><br>
> > > > It works on our test cluster where we have<br>
> > > > 2.6.32-openvz-042stab093.4-amd64 installed. The report from below is<br>
> > > > from a host node running 2.6.32-042stab081.3-amd64.<br>
> > > ><br>
> > > > Is ploop_userspace dependent on kernel version?<br>
> > > ><br>
> > > > Roman<br>
> > > ><br>
> > > ><br>
> > > > On Thu, 2014-08-28 at 15:59 +0200, Roman Haefeli wrote:<br>
> > > >> Hi Pavel<br>
> > > >><br>
> > > >> Your tool comes in handy. That is exactly what we'd need. However, I had<br>
> > > >> troubles using it. I did:<br>
> > > >><br>
> > > >> $ ploop_userspace /virtual/.snapshot/nightly.0/vz/private/2006/root.hdd/root.hdd<br>
> > > >><br>
> > > >> We process: /virtual/.snapshot/nightly.0/vz/private/2006/root.hdd/root.hdd<br>
> > > >> Ploop file size is: 4193255424<br>
> > > >> version: 1 disk type: 2 heads count: 16 cylinder count: 81920 sector count: 2048 size in tracks: 20480 size in sectors: 41943040 disk in use: 1953459801 first block offset: 2048 flags: 0<br>
> > > >> For storing 21474836480 bytes on disk we need 20480 ploop blocks<br>
> > > >> We have 1 BAT blocks<br>
> > > >> We have 262128 slots in 1 map<br>
> > > >> Number of non zero blocks in map: 3998<br>
> > > >> Please be careful because this disk used now! If you need consistent backup please stop VE<br>
> > > >> !!!ERROR!!! We can't found GPT table on this disk<br>
> > > >> !!!ERROR!!! We can't find ext4 signature<br>
> > > >> Set device /dev/nbd0 as read only<br>
> > > >> Try to found partitions on ploop device<br>
> > > >> First ploop partition was not detected properly, please call partx/partprobe manually<br>
> > > >> You could mount ploop filesystem with command: mount -r -o noload /dev/nbd0p1 /mnt<br>
> > > >><br>
> > > >><br>
> > > >> Despite the errors, I tried to mount the ploop-partition:<br>
> > > >><br>
> > > >> $ mount -r -o noload /dev/nbd0p1 /mnt/<br>
> > > >><br>
> > > >> and got:<br>
> > > >><br>
> > > >> mount: special device /dev/nbd0p1 does not exist<br>
> > > >><br>
> > > >> Apparently, ploop_userspace wasn't able to read the GPT partition table.<br>
> > > >><br>
> > > >> Tell me, if you need further information.<br>
> > > >><br>
> > > >> Thanks,<br>
> > > >> Roman<br>
> > > >><br>
> > > >><br>
> > > >><br>
> > > >><br>
> > > >><br>
> > > >><br>
> > > >><br>
> > > >><br>
> > > >> On Tue, 2014-08-19 at 12:48 +0400, Pavel Odintsov wrote:<br>
> > > >> > Hello!<br>
> > > >> ><br>
> > > >> > You can mount ploop from RO root.hdd images with my tool:<br>
> > > >> > <a href="https://github.com/FastVPSEestiOu/ploop_userspace" target="_blank">https://github.com/FastVPSEestiOu/ploop_userspace</a> but it's not stable<br>
> > > >> > now. You can try it and provide feedback.<br>
> > > >> ><br>
> > > >> > On Tue, Aug 19, 2014 at 12:24 PM, Roman Haefeli <<a href="javascript:;" onclick="_e(event, 'cvml', 'reduzent@gmail.com')">reduzent@gmail.com</a>> wrote:<br>
> > > >> > > Hi all<br>
> > > >> > ><br>
> > > >> > > At the university I work, we plan to switch all containers from simfs to<br>
> > > >> > > ploop images on the long run. Despite the many advantages of using<br>
> > > >> > > ploop, there is one major drawback that keeps us from switching<br>
> > > >> > > production already now: We can't mount ploop images from read-only<br>
> > > >> > > snapshots. In case of a recovery of a single file, we have to copy the<br>
> > > >> > > ploop image from the read-only snapshot to some read-write storage in<br>
> > > >> > > order to be able to mount it and extract the file. For CTs with huge<br>
> > > >> > > ploop-images this is a big hurdle.<br>
> > > >> > ><br>
> > > >> > > Wouldn't it be possible to add a some flag to the 'ploop' utility to<br>
> > > >> > > allow mounting ploop images from read-only storage (by bypassing some<br>
> > > >> > > checks or skipping to set the dirty flag or whatever is necessary)?<br>
> > > >> > ><br>
> > > >> > > Cheers,<br>
> > > >> > > Roman<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > _______________________________________________<br>
> > > >> > > Users mailing list<br>
> > > >> > > <a href="javascript:;" onclick="_e(event, 'cvml', 'Users@openvz.org')">Users@openvz.org</a><br>
> > > >> > > <a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
> > > >> ><br>
> > > >> ><br>
> > > >> ><br>
> > > >><br>
> > > >><br>
> > > ><br>
> > > ><br>
> > > > _______________________________________________<br>
> > > > Users mailing list<br>
> > > > <a href="javascript:;" onclick="_e(event, 'cvml', 'Users@openvz.org')">Users@openvz.org</a><br>
> > > > <a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
> > ><br>
> > ><br>
> > ><br>
> ><br>
> ><br>
><br>
><br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'Users@openvz.org')">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
</blockquote><br><br>-- <br>Sincerely yours, Pavel Odintsov<br>