Hi,
has anybody tried using the new ploop storage for openvz images together
with moosefs ( http://www.moosefs.org/)?
ploop mount -d /dev/ploop0 /mfs-mount/root.hdd
Adding delta dev=/dev/ploop0 img=/mfs-mount/root.hdd (rw)
PLOOP_IOC_ADD_DELTA /mfs-mount/root.hdd: Invalid argument
In syslog I
l Kolyshkin:
Ploop only supports ext4 and nfs
31.03.2012 22:50 "Corin Langosch" <mailto:i...@corinlangosch.com>> ???:
Hi,
has anybody tried using the new ploop storage for openvz images
together with moosefs ( http://www.moosefs.org/)?
ploop m
Am 02.04.2012 12:19, schrieb Aleksandar Ivanisevic:
Out of interest, have you tried running VEs off of moosefs, directly,
without ploop? How does that work, if at all?
Yes, but only for a quick test and not with any production data:
- setup moosefs as usual and mount it on host
- create (spar
Hi Kir,
Am 01.04.2012 14:11, schrieb Kir Kolyshkin:
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.
Sounds great. Ca
Am 02.04.2012 12:19, schrieb Aleksandar Ivanisevic:
Out of interest, have you tried running VEs off of moosefs, directly,
without ploop? How does that work, if at all?
Yes, but only for a quick test and not with any production data:
- setup moosefs as usual and mount it on host
- create (spar
Hi Joe,
Am 08.04.2012 00:48, schrieb jjs - mainphrame:
Thanks for the pointer to the article, that's good info. I've checked
my system, and I'm nowhere near the limit of space or inodes.
To further test, I create a ploop CT which contains the expected
amount of disk space.
I then create a sim
Hi Kir,
Am 06.04.2012 23:33, schrieb Kir Kolyshkin:
* NOTE ploop is not yet ready for production, and will not be for at
least a few more months.
Now this really confuses/ worries me as the latest *stable* release has
ploop support. If it's not stable (so not ready for production), why is
Hi there,
Is there any way to specify mount options for the container's root
filesystem in the container's config when using ploop?
So a normal options string like
"noatime,data=writeback,journal_async_commit,barrier=0,errors=remount-ro".
Thanks for any hints :)
Corin
_
ails with "mount: permission denied".
Now I wonder if this is intended or a bug? Why allow changing barrier
and deny noatime option?
BTW: I still haven't found a way to specify mount options in the
container's config :(
Corin
On 03.07.2012 at 09:52 +0200, Corin Langosc
Hi Vasily,
yes. Ploop creates a new block device on which you then create a new fs.
Corin
On 29.08.2012 at 09:41 +0200, Rene C. wrote:
Thanks everybody. Hm, that's a bit of a bummer.
Would using ploop fs change that? (I mean, I understand it won't fix
the present problem but for the future
ails with "mount: permission denied".
Now I wonder if this is intended or a bug? Why allow changing barrier
and deny noatime option?
BTW: I still haven't found a way to specify mount options in the
container's config :(
Corin
On 03.07.2012 at 09:52 +0200, Corin Langosc
On 08.09.2012 at 15:31 +0200, Kir Kolyshkin wrote:
In fact I just implemented that as a --mount_opts option to vzctl set.
See these git commits:
http://git.openvz.org/?p=vzctl;a=commit;h=af95fbdf
http://git.openvz.org/?p=vzctl;a=commit;h=287d0d
http://git.openvz.org/?p=vzctl;a=commit;h=7eb61
On 12.09.2012 at 14:21 +0200, Kir Kolyshkin wrote:
On 09/12/2012 03:59 PM, Corin Langosch wrote:
On 08.09.2012 at 15:31 +0200, Kir Kolyshkin wrote:
In fact I just implemented that as a --mount_opts option to vzctl
set. See these git commits:
http://git.openvz.org/?p=vzctl;a=commit;h
Hi,
it seems that when creating & deleting files inside a ploop backed
container the backing image file doesn't shrink. So the image file is
still consuming around 400 GB, while in the container df shows only 100
GB in use.
ll on host: -rw--- 1 root root 384G Sep 12 21:06 root.hdd
df on
Hi,
it seems that when creating & deleting files inside a ploop backed
container the backing image file doesn't shrink. So the image file is
still consuming around 400 GB, while in the container df shows only 100
GB in use.
ll on host: -rw--- 1 root root 384G Sep 12 21:06 root.hdd
df on
On 12.09.2012 at 21:34 +0200, Kir Kolyshkin wrote:
On Sep 12, 2012 11:20 PM, "Corin Langosch" <mailto:i...@corinlangosch.com>> wrote:
>
> Hi,
>
> it seems that when creating & deleting files inside a ploop backed
container the backing image file doesn&#x
On 13.09.2012 at 09:22 +0200, Kirill Korotaev wrote:
No, AFAIR we should use TRIM on ext4 and it simply reports unused space.
Balloon is used for "resize" via allocating some space and hiding it
from user, but for compacting it's a bit bad since can cause ENOSPC
while it's really not...
On 10.10.2012 at 18:25 +0200, Roman Haefeli wrote:
We're having issues with processes in a container being killed by OOM,
although the hostnode does not have even half of its memory used.
How can it be that there is a failcnt for oomguarpages, although the
barrier wasn't even reached?
This is o
18 matches
Mail list logo
