Hi Scott,
Ummm, you can still access the files inside of ploop-based container
when it isn't running... simply by mounting it. Is there an issue
with that?
Granted: It's probably more of a psychological or philosophical issue
than a technical one. Filesystem on a filesystem. That adds a
Greetings,
- Original Message -
If our users have to choose between no more inode issues or having
direct access to all VPS files and folders from the HN, then ploop
will probably always get the short end of the stick.
Ummm, you can still access the files inside of ploop-based
On 07/21/2015 07:56 PM, Scott Dowdle wrote:
Greetings,
- Original Message -
ZFS is really The Last Word in File Systems,
and now you can just use it for free,
without reinventing the wheel.
OpenVZ + ZFS or Virtuozzo + ZFS == atom bomb,
killer feature with horrible devastation power.
Greetings,
- Original Message -
But maybe someone has some talking points that would help me to
win some hearts and minds there?
The biggest feature of ploop is snapshots. Of course snapshots are also great
for backups too. Oh and those performance gains are good too. Another thing
On 22.07.2015 3:17, Kir Kolyshkin wrote:
simfs need for using OpenVZ with ZFS
Other why not simfs considerations are listed at
http://openvz.org/Ploop/Why#Before_ploop
there are three levels:
1. before ploop: simfs over ext4
2. with ploop: ext4 over ploop over ext4
3. after ploop: simfs
On 07/21/2015 06:41 PM, Gena Makhomed wrote:
For one thing, I wonder how you use live migration with zfs,
can you please tell us?
I don't use live migration at all.
several reasons:
1) currently even suspend/resume not work reliable:
https://bugzilla.openvz.org/show_bug.cgi?id=2470
- I
I will certainly take a look at the iostats and see if that will help. I was
tasked with doing this to find a user(s) that are chewing through the ssd disks
on one particular node. So I figured finding out who was doing all the writes
might help figure that out, and seemed to be until today and
Just one thing -- ioacct accounts on a VFS level, not on actual disk I/O
level.
Also, ioacct accounts all reads and writes, including tmpfs and /proc
and /sys etc.
Say, if you rewrite a file (a real file on disk) a thousand times real
quick, it does not
mean the data will be written to a disk
On 07/21/2015 08:51 AM, Michael Stauber wrote:
Hi Scott,
Ummm, you can still access the files inside of ploop-based container
when it isn't running... simply by mounting it. Is there an issue
with that?
Granted: It's probably more of a psychological or philosophical issue
than a technical
Greetings,
- Original Message -
ZFS is really The Last Word in File Systems,
and now you can just use it for free,
without reinventing the wheel.
OpenVZ + ZFS or Virtuozzo + ZFS == atom bomb,
killer feature with horrible devastation power.
Or - you just forcing users to migrate
Greetings,
- Original Message -
Maybe it's worth the thought to provide vzmigrate with an extension that
allows to vzmigrate from a simfs source VPS to ploop target VPS?
I can do that on foot (if need be) or hack some scripts together that
do the transition with or without a
On 22.07.2015 0:11, Kir Kolyshkin wrote:
The biggest problem with simfs appears to be security. We have recently
found a few bugs (not in simfs per se, but in the kernel in general,
i.e. these
are not our bugs for the most part) that can be exploited to escape
the simfs and let container access
Hi Scott,
vzctl has a convert option.
Oh? Nice. That must have slipped right by me. Thanks for pointing that out.
It seems like your argument is basically, because it was already
there and people don't have to learn anything to use them.
While that is true, it doesn't sound too compelling
Hello,
we want find people who still use simfs for OpenVZ containers.
Do we have such users?
Sergey B.
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users
Hi
Jira issues contains only requirements to features.
We hope to fix problem with hidden content by replacing current Bugzilla
with public Jira.
Anyway this TRD (Test Request Description) contains all necessary details
about new feature and these details are enough for people who want to
test
we want find people who still use simfs for OpenVZ containers.
Do we have such users?
All proxmox VE users (as we do not have ploop support).
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users
On 21.07.2015 10:21, Sergey Bronnikov wrote:
Hello,
we want find people who still use simfs for OpenVZ containers.
Do we have such users?
Solar with his rhel5-based Openwall distribution
___
Users mailing list
Users@openvz.org
First version of the script:
https://src.openvz.org/projects/OVZL/repos/ovztransfer/browse
How to use:
1. Clone script to source OpenVZ HN
2. Put the ssh key to destination HN for root user
3. Start script example:
./ovztransfer.sh 10.20.87.188 400:12345
: migrate Container 400 to 12345 on HN
I'm using mixed simfs/ploop.
Regards,
Volker
Am 21.07.2015 um 09:21 schrieb Sergey Bronnikov serg...@openvz.org:
Hello,
we want find people who still use simfs for OpenVZ containers.
Do we have such users?
Sergey B.
___
Users mailing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here!
_ hostcmd vz 'vzlist -Holayout | fgrep simfs' | wc -l
911
On 21.07.2015 09:21, Sergey Bronnikov wrote:
Hello,
we want find people who still use simfs for OpenVZ containers.
Do we have such users?
Sergey B.
Hi,
We have 150 containers running on simfs.
What do you need ?
Regards,
Le 21 juil. 2015 à 09:26, Sergey Bronnikov serg...@openvz.org a écrit :
Hello,
we want find people who still use simfs for OpenVZ containers.
Do we have such users?
Sergey B.
Hi Sergey,
we want find people who still use simfs for OpenVZ containers.
Do we have such users?
All Aventurin{e} users, as we'll only add ploop sometime later this
year. Even then simfs will remain the standard fs for new VPS's.
If our users have to choose between no more inode issues or
22 matches
Mail list logo
