<html>
<head>
<meta content="text/html; charset=KOI8-R" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 03/31/2012 11:13 PM, Corin Langosch wrote:
<blockquote cite="mid:4F775755.7090507@corinlangosch.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=KOI8-R">
Hi Kirill,<br>
<br>
thank you for your very fast response. :)<br>
<br>
Am 31.03.2012 20:54, schrieb Kirill Kolyshkin:
<blockquote
cite="mid:CAGmPdrwp7QbPrQqtsd+H=dgoabVMG8KaOGVtHzxAxZa82O-=dg@mail.gmail.com"
type="cite">
<p>Ploop only supports ext4 and nfs </p>
</blockquote>
Is there any special reason for this? I'd really like to know the
technical aspects because I then might be able to make moosefs (or
another fuse based fs developed by myself) working with ploop. If
I can read about it in any documents, please redirect me to them
:)<br>
</blockquote>
<br>
Ploop developers are now working on fuse I/O module for ploop (and
fuse improvements required for it). When this work will be ready,
you might revisit this issue and see what is required from moosefs
to be used for ploop.<br>
<br>
<blockquote cite="mid:4F775755.7090507@corinlangosch.com"
type="cite"> <br>
Another question: is it (easily) possible make an openvz container
use a normal block devices for storage (which is formatted with
ex. ext4)? Before seeing ploop I thought this won't be possible,
but now with ploop it seems vzctl is only mounting /dev/ploopX
somewhere and then using this mount as the container's root. I'd
especially be interested in using ex. an iscsi backed block device
with openvz containers.<br>
</blockquote>
<br>
Yes it's pretty possible, with some minor modifications to vzctl. I
need to think a bit more about it, but it looks like a trivial case
(no vzquota etc). Let me know if you want to work on that.<br>
<br>
<blockquote cite="mid:4F775755.7090507@corinlangosch.com"
type="cite"> <br>
Am 31.03.2012 20:54, schrieb Kirill Kolyshkin:
<blockquote
cite="mid:CAGmPdrwp7QbPrQqtsd+H=dgoabVMG8KaOGVtHzxAxZa82O-=dg@mail.gmail.com"
type="cite">
<p>Ploop only supports ext4 and nfs </p>
<div class="gmail_quote">31.03.2012 22:50 пользователь "Corin
Langosch" <<a moz-do-not-send="true"
href="mailto:info@corinlangosch.com">info@corinlangosch.com</a>>
написал:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi,<br>
<br>
has anybody tried using the new ploop storage for openvz
images together with moosefs ( <a moz-do-not-send="true"
href="http://www.moosefs.org/" target="_blank">http://www.moosefs.org/</a>)?<br>
<br>
ploop mount -d /dev/ploop0 /mfs-mount/root.hdd<br>
Adding delta dev=/dev/ploop0 img=/mfs-mount/root.hdd (rw)<br>
PLOOP_IOC_ADD_DELTA /mfs-mount/root.hdd: Invalid argument<br>
<br>
In syslog I find:<br>
kernel: File on FS without backing device<br>
<br>
I thought it might be because ploop needs direct-io
(right?), but mounting with direct-io enabled seems not to
be supported by moosefs:<br>
<br>
mfsmount -o direct_io /mfs-mount<br>
mfsmaster accepted connection with parameters:
read-write,restricted_ip ; root mapped to root:root<br>
fuse: unknown option `direct_io'<br>
<br>
Has anybody got it working somehow? :)<br>
<br>
Btw: I'll also post this question to the moosefs
mailinglist as I'm pretty sure the devs there might have
interesting answers too.<br>
<br>
Corin</div>
</blockquote>
</div>
</blockquote>
</blockquote>
<br>
</body>
</html>