| Re: Why the ploop become the default? [message #51622 is a reply to message #51379] |
Thu, 28 August 2014 08:12   |
bjdea1
Messages: 39
Registered: February 2009
|
Member |
|
|
Ales wrote on Thu, 01 May 2014 12:23yuri wrote on Wed, 30 April 2014 16:47The SIMFS already support all other FS.
My definitions of the words deprecated and supported are a bit different than yours...
Sure, simfs can work on other file systems as of now, but I think having user quotas in CTs is a prerequisite for labeling file systems as supported. Quotas work only on ext2/3/4 and that alone makes anything but ext4 unusable for many openvz use cases.
Don't get me wrong, having working quotas and BtrFS or ZFS specific functionality would be great. I just don't think openvz project has enough resources to accomplish all this.
I use "ZFS on Linux" (ZOL) with simfs and with quotas, on production servers. The trick is to create ZVOLS and then create ext4 filesystems on top of these. That gives you the benefits of an underlying "Copy On write" filesystem (ZOL) and the ext4 quotas on top, making everything work together.
I use ZOL for compression and stability, its just a much more precise Fileysystem than EXT4 alone. I also have the option of adding an SSD cache any time I need.
So far ZFS on linux Zvols with ext4 on top have been running smoothly for over 6 months.
The only issues I face are a slightly lower performance, but not by much, and updating ZOL is somewhat troublesome. ZOL is in the form of kernel modules which need to be compiled for each kernel update.
I want to upgrade everything to ploop but as pointed out, its not perfect by any means yet and I am still hesitant.
█Deasoft.com Hosting/Software
█AutoBillMe.com Billing Automation
[Updated on: Thu, 28 August 2014 08:17] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
