Show Table of Contents
6.5. Creating Distributed Volumes
This type of volume spreads files across the bricks in the volume.
Figure 6.2. Illustration of a Distributed Volume
Distributed volumes can suffer significant data loss during a disk or server failure because directory contents are spread randomly across the bricks in the volume.
Use distributed volumes where scalable storage and redundancy is either not important, or is provided by other hardware or software layers.
Create a Distributed Volume
gluster volume createcommand to create different types of volumes, and
gluster volume infocommand to verify successful volume creation.
- A trusted storage pool has been created, as described in Section 5.1, “Adding Servers to the Trusted Storage Pool”.
- Understand how to start and stop volumes, as described in Section 6.10, “Starting Volumes”.
- Run the
gluster volume createcommand to create the distributed volume.The syntax is
gluster volume create NEW-VOLNAME [transport tcp | rdma | tcp,rdma] NEW-BRICK...The default value for transport is
tcp. Other options can be passed such as
auth.reject. See Section 10.1, “Configuring Volume Options” for a full list of parameters.
Example 6.1. Distributed Volume with Two Storage Servers
# gluster volume create test-volume server1:/exp1/brick server2:/exp2/brick Creation of test-volume has been successful Please start the volume to access data.
Example 6.2. Distributed Volume over InfiniBand with Four Servers
# gluster volume create test-volume transport rdma server1:/exp1/brick server2:/exp2/brick server3:/exp3/brick server4:/exp4/brick Creation of test-volume has been successful Please start the volume to access data.
# gluster volume start VOLNAMEto start the volume.
# gluster volume start test-volume Starting test-volume has been successful
gluster volume infocommand to optionally display the volume information.The following output is the result of Example 6.1, “Distributed Volume with Two Storage Servers”.
# gluster volume info Volume Name: test-volume Type: Distribute Status: Created Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: server1:/exp1/brick Brick2: server2:/exp2/brick