| Creating ploop device fails on zfs storage [message #49176] |
Fri, 05 April 2013 21:39  |
PyotrVelikiy
Messages: 3
Registered: May 2012
Location: United States
|
Junior Member |
|
|
Hello, using
ploop-1.6-1.x86_64
vzkernel-2.6.32-042stab076.5.x86_64
zfs-0.6.1-1.el6.x86_64
creating a CT fails when attempting to use ploop on a zfs /vz/private partition:
# vzctl create 1000 --ostemplate ubuntu-12.04-x86_64 --layout ploop --diskspace 8G
Creating image: /vz/private/1000.tmp/root.hdd/root.hdd size=8388608K
Creating delta /vz/private/1000.tmp/root.hdd/root.hdd bs=2048 size=16777216 sectors
Error in create_empty_delta (ploop.c:289): Can't open /vz/private/1000.tmp/root.hdd/root.hdd: Invalid argument
Failed to create image: Error in create_empty_delta (ploop.c:289): Can't open /vz/private/1000.tmp/root.hdd/root.hdd: Invalid argument [1]
Creation of container private area failed
Is this to be expected under zfs?
Is there a known workaround?
The same container works fine with default simfs on the same zfs partition.
|
|
|
|
|
|
| Re: Creating ploop device fails on zfs storage [message #49295 is a reply to message #49183] |
Thu, 18 April 2013 19:08  |
PyotrVelikiy
Messages: 3
Registered: May 2012
Location: United States
|
Junior Member |
|
|
The question is not what fs needs to be inside a ploop container;
it is why the creation of /vz/private/{ctid}/root.hdd/root.hdd
fails when /vz/private is a zfs partition.
According to wiki.openvz.org/Ploop/Why
"Different containers may use file systems of different types and properties"
So one might have hoped that user-space ploop can also use
zfsonlinux file systems.
|
|
|
|
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
