RozoFS

From Wikipedia, the free encyclopedia
Jump to: navigation, search
RozoFS
Rozofs-512.png
Developer(s) Rozo Systems, SAS.
Stable release
1.5.4 / 17 November 2014 (2014-11-17)
Development status Active
Written in C and Python
Operating system Linux, Mac OS X, NetBSD, FreeBSD, OpenSolaris
Type Distributed file system
License GNU General Public License v2
Website rozosystems.com

RozoFS is a free software distributed file system. It comes as a free software, licensed under the GNU GPL v2. RozoFS uses erasure coding for redundancy.[1][improper synthesis?]

Design[edit]

Rozo provides an open source POSIX filesystem, built on top of distributed file system architecture similar to Google File System, Lustre or Ceph. The Rozo specificity lies in the way data is stored. The data to be stored is translated into several chunks using Mojette Transform[2] and distributed across storage devices in such a way that it can be retrieved even if several pieces are unavailable. On the other hand, chunks are meaningless alone.[3] Redundancy schemes based on coding techniques like the one used by RozoFS allow to achieve significant storage savings as compared to simple replication.[4][5]

The file system comprises three components:

  • Exports server — (Meta Data Server) manages the location (layout) of chunks (managing capacity load balancing with respect to high availability), file access and namespace (hierarchy). Multiple replicated metadata servers are used to provide failover.The Exports server is a user-space daemon; the metadata are stored synchronously to a usual file system (the underlying file system must support extended attributes).
  • Storage servers — (Chunk Server) store the chunks. The Chunk server is also a user-space daemon that relies on the underlying local file system to manage the actual storage.
  • Clients — talk to both the exports server and chunk servers and are responsible for data transformation. Clients mount the file system into user-space via FUSE.

Rozo Systems was invited at the SNIA Data Storage Innovation conference in June 2016.[6]

See also[edit]

References[edit]

  1. ^ ZHANG, Z., DESHPANDE, A., MA, X., THERESKA, E., AND NARAYANAN (May 2010). "Does erasure coding have a role to play in my data center?" (PDF). Tech. Rep. MSR-TR-2010-52. Microsoft Research. 
  2. ^ Jeanpierre, Guédon (2009). The Mojette Transform theory and applications. ISTE-WILEY. ISBN 9781848210806. 
  3. ^ J. P. Guédon; B. Parrein; N. Normand (August 2001). "Secure Distributed Storage based on the Mojette transform". Integrated Computer-Aided Engineering v.8 n.3: 205–214. 
  4. ^ Weatherspoon, Hakim and Kubiatowicz, John (2002). "Erasure Coding Vs. Replication: A Quantitative Comparison". Revised Papers from the First International Workshop on Peer-to-Peer Systems. IPTPS '01. Springer-Verlag: 328–338. 
  5. ^ Rodrigues, Rodrigo & Liskov, Barbara (2005). "High availability in DHTs: erasure coding vs. replication". Proceedings of the 4th international conference on Peer-to-Peer Systems. IPTPS'05. Springer-Verlag: 226–239. doi:10.1007/11558989_21. 
  6. ^ Nicolas, Philippe (June 14, 2016). "High Performance NAS, New design for New IT Challenges". 

Press articles[edit]

External links[edit]