CT storage backends - Revision history

189.48.165.221: Some ZFS fixes and updates

2022-12-15T18:02:42Z

Some ZFS fixes and updates

Vvs at 18:19, 24 September 2020

2020-09-24T18:19:01Z

Sergey Bronnikov: return back row with 'Shared storage support', merge three tables to single table

2016-06-07T11:09:35Z

return back row with 'Shared storage support', merge three tables to single table

Sergey Bronnikov: ZFS is not a SimFS

2016-06-07T10:04:31Z

ZFS is not a SimFS

Narcisgarcia: /* Administrator operations */

2016-06-06T13:22:40Z

‎Administrator operations

Narcisgarcia: /* Solidity in front of failures and security */

2016-06-06T13:21:05Z

‎Solidity in front of failures and security

Narcisgarcia: References, vzctl integration

2016-06-06T13:16:37Z

References, vzctl integration

Narcisgarcia: Reorganization, deduplication, +LVM +ZFS

2016-06-06T13:05:34Z

Reorganization, deduplication, +LVM +ZFS

Show changes

Sergey Bronnikov: Marked this version for translation

2015-12-25T23:28:20Z

Marked this version for translation

Sergey Bronnikov: add 'translate' tags

2015-12-25T23:25:05Z

add 'translate' tags

@@ Line 37: / Line 37: @@
 |No
 |No
-|?
+|{{Yes|Using zvol}}
 |-
 |'''Effect of HN filesystem corruption at /vz'''
@@ Line 63: / Line 63: @@
 |No
 |Up to 20%
-|?
+|No, but if using zvol is up to 50% depending on volblocksize
 |-
 |'''Disk I/O speed'''
@@ Line 80: / Line 80: @@
 |{{Yes}}
 |{{No}}
-|Yes
+|{{Yes}}
-|No
+|{{Yes|Using zvol}}
 |-
 |'''Second level quotes in Linux (inside container)'''
@@ Line 87: / Line 87: @@
 |{{Yes}}
 |{{Yes}}
-|{{No|Not implemented}}
+|{{Yes|Using zvol}}
 |-
 |'''Potential support for QCOW2 and other image formats'''
@@ Line 93: / Line 93: @@
 |{{No}}
 |{{No}}
-|No
+|{{No}}
 |-
 |'''Incremental backup support on filesystem level'''
@@ Line 105: / Line 105: @@
 |{{No|No}}
 |{{Yes|Yes}}
-|?
+|{{Yes|NFS only}}
 |-
 !colspan="11" style="font-style:bold;background-color:gold;"|3. Maintenance
@@ Line 125: / Line 125: @@
 |{{Yes}}
 |?
-|?
+|{{Yes|Only using ZFS filesystem}}
 |-
 |'''Live backup'''
 |{{Yes|Easy, fast and consistent}}<ref>[http://openvz.livejournal.com/44508.html ploop snapshots and backups]</ref> <ref>[[Ploop/Backup]]</ref>
 |{{No|Easy, slow, and sometimes inconsistent}} in case some application depends on inode IDs
-|{{No|Fast}}
+|{{No|No}}
-|{{Yes|Fast}} theoretically
+|{{Yes|Fast}} via ZFS Send/Receive
 |-
 |'''Snapshot support'''
@@ Line 143: / Line 143: @@
 |{{No|Not reliable and slow}}, if some application depends on inode IDs
 |{{No|Not implemented}}
-|{{Yes|Fast}} theoretically
+|{{Yes|Fast}} via ZFS Send/Receive
 |-
 |'''Continue failed CT migration'''

@@ Line 46: / Line 46: @@
 |-
 |'''Maturity in O/VZ'''
-|{{No|Since 2012}}
+|{{Yes|Since 2012}}
 |{{Yes|Since ~2005}}
 |{{Yes|Since 1998}}
-|{{No|Since 2014}}
+|{{Yes|Since 2014}}
 |-
 !colspan="11" style="font-style:bold;background-color:gold;"|2. Performance and design features

@@ Line 1: / Line 1: @@
 {{stub}}
 <translate>
-= Comparison tables =
 <!--T:1-->
 {| class="wikitable sortable" style="text-align: center;"
 ! Feature
 ! OVZ Ploop
@@ Line 11: / Line 12: @@
 ! LVM (ext4)
 ! ZFS
 |-
 |'''I/O isolation'''
 |{{Yes|Good}}
-|{{No|Bad}}: Some bug could be exploited to escape CT and access HN file system <ref>[https://bugs.openvz.org/browse/OVZ-6296 CVE-2015-2925]</ref> <ref>[http://www.openwall.com/lists/oss-security/2014/06/24/16 CVE-2014-3519]</ref>
+|{{No|Bad}}: Possibility of "no inodes" issues (when file system journal become a bottleneck).
 |{{Yes|Good}}
 |{{Yes|Good}}
 |-
 |'''Reliability'''
@@ Line 25: / Line 34: @@
 |-
 |'''Filesystem over filesystem'''
-|{{No|Yes}}
+|Yes
-|{{Yes|No}}
+|No
-|{{Yes|No}}
+|No
 |?
 |-
 |'''Effect of HN filesystem corruption at /vz'''
-|{{Yes|No effect}}
+|{{Yes|No corruption}}
-|{{No|Same FS}}
+|{{No|Possible corruption}}
 |?
 |?
@@ Line 42: / Line 51: @@
 |{{No|Since 2014}}
 |-
-|}
+!colspan="11" style="font-style:bold;background-color:gold;"|2. Performance and design features
 |-
 |'''Maximum container volume space'''
@@ Line 58: / Line 59: @@
 |256 ZiB
 |-
-|'''Wasted space due to architecture'''
+|'''Disk space overhead'''
-|{{No|up to 20%}}
+|Up to 20%
-|{{Yes|No}}
+|No
-|{{No|up to 20%}}
+|Up to 20%
 |?
 |-
-|'''Disk i/o speed'''
+|'''Disk I/O speed'''
-|Fast in any case
+|Fast
-|Very fast with small amount of containers
+|Fast only with small amount of containers per node, slowdown in case of big number of small files.
-|Fast in any case
+|Fast
-|Fast in any case
+|Fast
 |-
 |'''Disk space overcommit (provide more space for containers than available on server now)'''
@@ Line 100: / Line 101: @@
 |{{Yes}}
 |-
-|}
+|'''Shared storage support (Virtuozzo storage, NFS)'''
+|{{Yes|Yes}}
-=== Administrator operations ===
+|{{No|No}}
-{| class="wikitable sortable" style="text-align: center;"
+|{{Yes|Yes}}
-! Feature
+|?
-! OVZ Ploop
+|-
-! OVZ SimFS (ext4)
+!colspan="11" style="font-style:bold;background-color:gold;"|3. Maintenance
 |-
 |'''vzctl integration'''

@@ Line 10: / Line 10: @@
 ! OVZ SimFS (ext4)
 ! LVM (ext4)
-! ZFS (~simfs)
+! ZFS
 |-
 |'''I/O isolation'''

@@ Line 113: / Line 113: @@
 |{{Yes|Complete}}
 |{{Yes|Complete}}
-|{{No|No}}, many manual operations
+|{{No}}, many manual operations
-|{{Yes|No}}, some manual operations
+|{{No}}, some manual operations
 |-
 |'''External compaction for container volumes'''