<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 28 January 2014 02:55, Kirill Korotaev <span dir="ltr"><<a href="mailto:dev@parallels.com" target="_blank">dev@parallels.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">>> On 25 Jan 2014, at 07:38, Rene C. <a href="mailto:openvz@dokbua.com">openvz@dokbua.com</a> wrote:<br>
>><br>
><br>
> Hi,<br>
><br>
> I read the website about the cloud storage and I found some words, which seems familiar for me.<br>
><br>
> May I ask, which filesystem do you use to be able to regularly scrub and self-heal the filesystem?<br>
><br>
> Personaly I use zfsonlinux in production for a long time now and I am very satisfied with it, and based on your description, it seems you should use something like that and something on top of the native filesystem to get a cloud storage.<br>
><br>
> Or you use a ceph or alike "filesystem", which has similar capabilities with cloud features.<br>
<br>
</div>It’s more like a ceph. Data is stored in a distributed way, so unlike to zfs you have access to the data even in case of node failure (crash, CPU/memory fault etc.) and access is available from ANY cluster node.<br>
As such we store the data and maintain checksums on every node and can do periodic scrubbing of the data.<br></blockquote><div><br></div><div>Just to clarify -- this is Parallels own distributed/cloud filesystem, not CEPH or GlusterFS,</div>
<div>but similar to. For more info, check the links at <a href="https://openvz.org/Parallels_Cloud_Storage#External_links">https://openvz.org/Parallels_Cloud_Storage#External_links</a></div></div><br></div></div>