OpenVZ Forum: Discussions » Why the ploop become the default?

Home » General » Discussions » Why the ploop become the default? (There's no reason to abandon the SIMFS in most cases)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Why the ploop become the default? [message #51379 is a reply to message #51377]

Thu, 01 May 2014 02:23

Ales
Messages: 330
Registered: May 2009

Senior Member

yuri wrote on Wed, 30 April 2014 16:47

The 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.

Report message to a moderator

[Message index]

		Why the ploop become the default? By: yuri on Sun, 27 April 2014 15:15
		Re: Why the ploop become the default? By: Ales on Tue, 29 April 2014 10:56
		Re: Why the ploop become the default? By: yuri on Wed, 30 April 2014 14:47
		Re: Why the ploop become the default? By: Ales on Thu, 01 May 2014 02:23
		Re: Why the ploop become the default? By: bjdea1 on Thu, 28 August 2014 08:12
		Re: Why the ploop become the default? By: mangust on Sun, 03 September 2017 02:48

Previous Topic:	Automated dedicated server transfer possible?
Next Topic:	OpenVZ isn't pingable after reboot

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Sep 06 21:35:45 GMT 2026

Total time taken to generate the page: 0.06091 seconds