linux_wiki:glusterfs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
linux_wiki:glusterfs [2015/10/04 23:08]
billdozor
linux_wiki:glusterfs [2019/05/25 23:50] (current)
Line 10: Line 10:
  
 **Checklist** **Checklist**
-  * Distro: Enterprise Linux 6+  * Distro(s): Enterprise Linux 6
  
 ---- ----
Line 139: Line 139:
     * <code bash>gluster volume add-brick myvol server5:/data/glusterfs/myvol/brick1/brick</code>     * <code bash>gluster volume add-brick myvol server5:/data/glusterfs/myvol/brick1/brick</code>
   * Remove a brick from the volume (and then remove from trusted storage pool)   * Remove a brick from the volume (and then remove from trusted storage pool)
-    * <code bash>gluster volume remove-brick myvol server2:/data/glusterfs/myvol/brick1/brick</code>+    * <code bash>gluster volume remove-brick myvol server2:/data/glusterfs/myvol/brick1/brick start 
 +gluster volume remove-brick myvol server2:/data/glusterfs/myvol/brick1/brick status 
 +gluster volume remove-brick myvol server2:/data/glusterfs/myvol/brick1/brick commit</code> 
 +    * Gluster will auto-rebalance data between the remaining bricks. 
 +    * If any type of replication or stripe sets exist, you must remove a number of bricks equal to a multiple.
   * Replace a faulty brick   * Replace a faulty brick
     * <code bash>gluster volume replace-brick myvol server3:/data/glusterfs/myvol/brick1/brick server5:/data/glusterfs/myvol/brick1/brick commit force</code>     * <code bash>gluster volume replace-brick myvol server3:/data/glusterfs/myvol/brick1/brick server5:/data/glusterfs/myvol/brick1/brick commit force</code>
 +  * Start Volume
 +    * <code bash>gluster volume start myvol</code>
 +  * Stop Volume
 +    * <code bash>gluster volume stop myvol</code>
  
 ==== Balance Data ==== ==== Balance Data ====
  • linux_wiki/glusterfs.1444014514.txt.gz
  • Last modified: 2019/05/25 23:50
  • (external edit)