C Makefile Shell Roff M4 CSS Other
Permalink
Failed to load latest commit information.
debian (mount+tools) increased masterproxy timeout from 1s to 20s Jul 12, 2018
freebsd (all) version 3.0.101 Jul 5, 2018
m4 MooseFS 2.0.60-1 Jan 27, 2016
macosx MooseFS 3.0.57-1 Jan 27, 2016
mfschunkserver (cs) fixed metaid handling Jul 5, 2018
mfscommon (all) added 'nobreak' macro to explicitly inform compiler that intent… May 16, 2018
mfsdata (all) added new options to manpages and sample config files Jul 5, 2018
mfsmanpages (all) version 3.0.101 Jul 5, 2018
mfsmaster (master) added optional same rack preference for destination server d… Jul 5, 2018
mfsmetadump (all) version updated to 3.0.100 (and year 2017 -> 2018) Jan 25, 2018
mfsmetalogger (all) version updated to 3.0.100 (and year 2017 -> 2018) Jan 25, 2018
mfsmount (mount+tools) increased masterproxy timeout from 1s to 20s Jul 12, 2018
mfsnetdump (all) version updated to 3.0.100 (and year 2017 -> 2018) Jan 25, 2018
mfsscripts (cgiserv) fixed handling connection close during data sending (leavin… May 16, 2018
mfssupervisor (all) fixed library dependencies (for libpcap,libz and libm) Nov 9, 2017
mfstests (all) version updated to 3.0.100 (and year 2017 -> 2018) Jan 25, 2018
rpm (all) version 3.0.101 Jul 5, 2018
systemd (debian) added support for systemd in debian packages, (all) added sy… Nov 8, 2017
COPYING MooseFS 3.0.72-1 Feb 24, 2016
INSTALL MooseFS 2.0.60-1 Jan 27, 2016
Makefile.am (all) fixed library dependencies (for libpcap,libz and libm) Nov 9, 2017
Makefile.in (all) fixed library dependencies (for libpcap,libz and libm) Nov 9, 2017
NEWS (mount+tools) increased masterproxy timeout from 1s to 20s Jul 12, 2018
README Updated README.md and README Jul 19, 2018
README.md Updated README.md and README Jul 19, 2018
aclocal.m4 (all) fixed library dependencies (for libpcap,libz and libm) Nov 9, 2017
compile (all) fixed library dependencies (for libpcap,libz and libm) Nov 9, 2017
config.guess MooseFS 2.0.60-1 Jan 27, 2016
config.h.in (all) added new options to manpages and sample config files Jul 5, 2018
config.sub MooseFS 2.0.60-1 Jan 27, 2016
configure (all) version 3.0.101 Jul 5, 2018
configure.ac (all) version 3.0.101 Jul 5, 2018
debian_sysv_to_systemd.sh (debian) fixed dependencies (python3 and dh-systemd) May 16, 2018
depcomp (all) fixed library dependencies (for libpcap,libz and libm) Nov 9, 2017
freebsd_build.sh MooseFS 2.0.60-1 Jan 27, 2016
install-sh MooseFS 2.0.60-1 Jan 27, 2016
linux_build.sh MooseFS 2.0.60-1 Jan 27, 2016
ltmain.sh MooseFS 3.0.74-1 Mar 9, 2016
macosx_build.sh MooseFS 3.0.61-1 Jan 27, 2016
missing (all) fixed library dependencies (for libpcap,libz and libm) Nov 9, 2017
sanitize_build.sh MooseFS 3.0.62-1 Jan 27, 2016
test-driver MooseFS 2.0.60-1 Jan 27, 2016

README.md

MooseFS logo

MooseFS - A Petabyte Distributed File System

MooseFS is a Petabyte Open Source Network Distributed File System. It is easy to deploy and maintain, fault tolerant, highly performing, easily scalable, POSIX compliant.

MooseFS spreads data over several physical commodity servers, which are visible to the user as one big volume. For standard file operations MooseFS acts like ordinary Unix-like file system:

  • A hierarchical structure (directory tree)
  • Stores POSIX file attributes (permissions, last access and modification times, etc.)
  • Supports ACLs
  • Supports POSIX and BSD locks
  • Supports special files (block and character devices, pipes and sockets)
  • Symbolic links (file names pointing to target files, not necessarily on MooseFS) and hard links (different names of files which refer to the same data on MooseFS)

Distinctive MooseFS features:

  • High reliability - configurable number of files' copies are stored on separate servers
  • No Single Point of Failure - all hardware and software components may be redundant
  • Parallel data operations - many clients can access many files concurrently
  • Capacity can be dynamically expanded by simply adding new computers/disks on the fly
  • Retired hardware may be removed on the fly
  • Deleted files are retained for a configurable period of time (a file system level "trash bin")
  • Coherent, "atomic" snapshots of files, even while the files are being written/accessed
  • Access to the file system can be limited based on IP address and/or password (similarly as in NFS)
  • Data tiering - supports different storage policies for different files/directories
  • Efficient, pure C implementation
  • Ethernet support

Supported platforms

MooseFS can be installed on any POSIX compliant operating system including different Linux distributions, FreeBSD, OS X:

  • Ubuntu
  • Debian
  • RHEL/CentOS
  • OpenSUSE
  • FreeBSD
  • MacOS X
  • Raspbian - Raspberry Pi 3

MooseFS Client uses FUSE.

There is a separate MooseFS Client for MS Windows available, built on top of Dokany.

Getting started

You can install MooseFS using your favourite package manager on one of the following platforms using officially supported repositories:

  • Ubuntu 14/16/18
  • Debian 8/9
  • RHEL/CentOS 6/7
  • FreeBSD 9.3/10/11
  • MacOS X 10.9-10.13
  • Raspbian 8 (Jessie) - Raspberry Pi 3

Minimal set of packages, which are needed to run MooseFS:

  • moosefs-master MooseFS Master Server for metadata servers,
  • moosefs-chunkserver MooseFS Chunkserver for data storage servers,
  • moosefs-client MooseFS Client - client side package to mount the filesystem.

Source code

Feel free to download source code either from GitHub code repository or from our website archives.

Install the following dependencies before building MooseFS from sources:

  • Debian/Ubuntu: sudo apt install build-essential libpcap-dev zlib1g-dev libfuse-dev pkg-config
  • CentOS/RHEL: sudo yum install gcc make libpcap-devel zlib-devel fuse-devel pkgconfig

Recommended packages:

  • Debian/Ubuntu: sudo apt install fuse
  • CentOS/RHEL: sudo yum install fuse

Building MooseFS on Linux can be easily done by running ./linux_build.sh. Similarly, use ./freebsd_build.sh in order to build MooseFS on FreeBSD and respectively ./macosx_build.sh on MacOS X. Remember, that those scripts do not install (i.e. do not run make install at the end). Run this command manually.

Minimal setup

Just three steps to have MooseFS up and running:

1. Install at least one Master Server

  1. Install moosefs-master package
  2. Prepare default config (as root):
cd /etc/mfs
cp mfsmaster.cfg.sample mfsmaster.cfg
cp mfsexports.cfg.sample mfsexports.cfg
  1. Prepare the metadata file (as root):
cd /var/lib/mfs
cp metadata.mfs.empty metadata.mfs
chown mfs:mfs metadata.mfs
rm metadata.mfs.empty
  1. Run Master Server (as root): mfsmaster start
  2. Make this machine visible under mfsmaster name (e.g. by adding a DNS entry or adding it in /etc/hosts on all servers)

2. Install at least two Chunkservers

  1. Install moosefs-chunkserver package
  2. Prepare default config (as root):
cd /etc/mfs
cp mfschunkserver.cfg.sample mfschunkserver.cfg
cp mfshdd.cfg.sample mfshdd.cfg
  1. At the end of mfshdd.cfg file make one or more entries containing paths to HDDs / partitions designated for storing chunks, e.g.:
/mnt/chunks1
/mnt/chunks2
/mnt/chunks3

It is recommended to use XFS as an underlying filesystem for disks designated to store chunks.

  1. Change the ownership and permissions to mfs:mfs to above mentioned locations, e.g.:
chown mfs:mfs /mnt/chunks1 /mnt/chunks2 /mnt/chunks3
chmod 770 /mnt/chunks1 /mnt/chunks2 /mnt/chunks3
  1. Start the Chunkserver: mfschunkserver start

Repeat steps above for second (third, ...) Chunkserver.

3. Client side: mount MooseFS filesystem

  1. Install moosefs-client fuse libfuse2 packages
  2. Mount MooseFS (as root):
mkdir /mnt/mfs
mount -t moosefs mfsmaster: /mnt/mfs

or: mfsmount -H mfsmaster /mnt/mfs

  1. You can also add an /etc/fstab entry to mount MooseFS during the system boot:
mfsmaster:    /mnt/mfs    moosefs    defaults,mfsdelayedinit    0 0

There are more configuration parameters available but most of them may stay with defaults. We do our best to keep MooseFS easy to deploy and maintain.

MooseFS, for testing purposes, can even be installed on a single machine!

Additional tools

Setting up moosefs-cli or moosefs-cgi both with moosefs-cgiserv is also recommended - it gives you a possibility to monitor the cluster online:

  1. Install moosefs-cli moosefs-cgi moosefs-cgiserv packages (they are typically set up on the Master Server)
  2. Run MooseFS CGI Server (as root): mfscgiserv start
  3. Open http://mfsmaster:9425 in your web browser

It is also strongly recommended to set up at least one Metalogger on a different machine than Master Server (e.g. on one of Chunkservers). Metalogger constantly synchronizes and backups the metadata:

  1. Install moosefs-metalogger package
  2. Prepare default config (as root):
cd /etc/mfs
cp mfsmetalogger.cfg.sample mfsmetalogger.cfg
  1. Run Metalogger (as root): mfsmetalogger start

Refer to installation guides for more details.

Some facts

Contact us

Copyright

Copyright (c) 2018 Jakub Kruszona-Zawadzki, Core Technology Sp. z o.o.

This file is part of MooseFS.

MooseFS is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, version 2 (only).

MooseFS is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with MooseFS; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02111-1301, USA or visit http://www.gnu.org/licenses/gpl-2.0.html.