Setting up a cluster filesystem

Revision as of 05:57, 8 November 2016 by AmitayIsaacs (talk | contribs) (Created page with "= Goal = Set up a clustered file system to be used with CTDB for providing clustered file services. In addition, * How to test if posix locking is supported on the file sys...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Goal

Set up a clustered file system to be used with CTDB for providing clustered file services.

In addition,

  • How to test if posix locking is supported on the file system?
  • Limitations when using clustered file system

Setting up clustered file system has nothing to do with CTDB. This information is provided for completeness. Users should be aware of any limitations of particular clustered file system.

Cluster file systems

Components

Any cluster file system will have some or all of following components:

  • Shared or distributed storage
  • Kernel or user space file system driver
  • User space file system daemon(s)
  • User space distributed lock manager
  • User space tools for management

Limitations

Every clustered file system has its quirks and limitations. Some of the file system limitations will affect the configuration of file services (Samba or NFS).

  • Does file system provide a consistent view across all the nodes (for example - uniform device and inode numbering) ?
  • Does file system provide posix locking semantics (cluster-aware locking)?
  • Does file system have specific quorum requirements?

Implementation

Each clustered file system example will describe how to set up a clustered file system for 3 node cluster. The implementation can be scaled down to 2 nodes or scaled up to more nodes.

GPFS

GFS

OCFS2

Add your favourite clustered file system here