gluster · amarts · Nov 24, 2020 · Jan 3, 2019 · Nov 18, 2020 · Nov 18, 2020
diff --git a/docs/Administrator Guide/Storage Pools.md b/docs/Administrator Guide/Storage Pools.md
diff --git a/docs/Administrator Guide/index.md b/docs/Administrator Guide/index.md
diff --git a/...ministrator Guide/Access Control Lists.md → ...ministrator-Guide/Access-Control-Lists.md b/...ministrator Guide/Access Control Lists.md → ...ministrator-Guide/Access-Control-Lists.md
diff --git a/...r Guide/Accessing Gluster from Windows.md → ...r-Guide/Accessing-Gluster-from-Windows.md b/...r Guide/Accessing Gluster from Windows.md → ...r-Guide/Accessing-Gluster-from-Windows.md
diff --git a/docs/Administrator Guide/Bareos.md → docs/Administrator-Guide/Bareos.md b/docs/Administrator Guide/Bareos.md → docs/Administrator-Guide/Bareos.md
diff --git a/...strator Guide/Brick Naming Conventions.md → ...strator-Guide/Brick-Naming-Conventions.md b/...strator Guide/Brick Naming Conventions.md → ...strator-Guide/Brick-Naming-Conventions.md
diff --git a/...MU With gfapi For Debian Based Systems.md → ...MU-With-gfapi-For-Debian-Based-Systems.md b/...MU With gfapi For Debian Based Systems.md → ...MU-With-gfapi-For-Debian-Based-Systems.md
diff --git a/docs/Administrator Guide/Consul.md → docs/Administrator-Guide/Consul.md b/docs/Administrator Guide/Consul.md → docs/Administrator-Guide/Consul.md
diff --git a/docs/Administrator Guide/Directory Quota.md → docs/Administrator-Guide/Directory-Quota.md b/docs/Administrator Guide/Directory Quota.md → docs/Administrator-Guide/Directory-Quota.md
diff --git a/docs/Administrator Guide/Events APIs.md → docs/Administrator-Guide/Events-APIs.md b/docs/Administrator Guide/Events APIs.md → docs/Administrator-Guide/Events-APIs.md
diff --git a/...ide/Export And Netgroup Authentication.md → ...ide/Export-And-Netgroup-Authentication.md b/...ide/Export And Netgroup Authentication.md → ...ide/Export-And-Netgroup-Authentication.md
diff --git a/docs/Administrator Guide/Geo Replication.md → docs/Administrator-Guide/Geo-Replication.md b/docs/Administrator Guide/Geo Replication.md → docs/Administrator-Guide/Geo-Replication.md
diff --git a/docs/Administrator Guide/Gluster On ZFS.md → docs/Administrator-Guide/Gluster-On-ZFS.md b/docs/Administrator Guide/Gluster On ZFS.md → docs/Administrator-Guide/Gluster-On-ZFS.md
diff --git a/docs/Administrator Guide/GlusterFS Cinder.md → docs/Administrator-Guide/GlusterFS-Cinder.md b/docs/Administrator Guide/GlusterFS Cinder.md → docs/Administrator-Guide/GlusterFS-Cinder.md
diff --git a/...dministrator Guide/GlusterFS Coreutils.md → ...dministrator-Guide/GlusterFS-Coreutils.md b/...dministrator Guide/GlusterFS Coreutils.md → ...dministrator-Guide/GlusterFS-Coreutils.md
diff --git a/docs/Administrator Guide/GlusterFS Filter.md → docs/Administrator-Guide/GlusterFS-Filter.md b/docs/Administrator Guide/GlusterFS Filter.md → docs/Administrator-Guide/GlusterFS-Filter.md
diff --git a/...nistrator Guide/GlusterFS Introduction.md → ...nistrator-Guide/GlusterFS-Introduction.md b/...nistrator Guide/GlusterFS Introduction.md → ...nistrator-Guide/GlusterFS-Introduction.md
@@ -16,7 +16,7 @@ Gluster is a scalable, distributed file system that aggregates disk storage reso
   * Open Source
 
 
-![640px-glusterfs_architecture](../images/640px-GlusterFS_Architecture.png)
+![640px-glusterfs_architecture](../images/640px-GlusterFS-Architecture.png)
 
 
 

diff --git a/...or Guide/GlusterFS Keystone Quickstart.md → ...or-Guide/GlusterFS-Keystone-Quickstart.md b/...or Guide/GlusterFS Keystone Quickstart.md → ...or-Guide/GlusterFS-Keystone-Quickstart.md
diff --git a/docs/Administrator Guide/GlusterFS iSCSI.md → docs/Administrator-Guide/GlusterFS-iSCSI.md b/docs/Administrator Guide/GlusterFS iSCSI.md → docs/Administrator-Guide/GlusterFS-iSCSI.md
diff --git a/...ide/Handling-of-users-with-many-groups.md → ...ide/Handling-of-users-with-many-groups.md b/...ide/Handling-of-users-with-many-groups.md → ...ide/Handling-of-users-with-many-groups.md
diff --git a/docs/Administrator Guide/Hook-scripts.md → docs/Administrator-Guide/Hook-scripts.md b/docs/Administrator Guide/Hook-scripts.md → docs/Administrator-Guide/Hook-scripts.md
@@ -1,23 +1,22 @@
 # Managing GlusterFS Volume Life-Cycle Extensions with Hook Scripts
 
-
 Glusterfs allows automation of operations by user-written scripts. For every operation, you can execute a *pre* and a *post* script.
 
 ### Pre Scripts
 These scripts are run before the occurrence of the event. You can write a script to automate activities like managing system-wide services. For example, you can write a script to stop exporting the SMB share corresponding to the volume before you stop the volume.
 
-### Post Scripts 
+### Post Scripts
 These scripts are run after execution of the event. For example, you can write a script to export the SMB share corresponding to the volume after you start the volume.
 
 You can run scripts for the following events:
 
-    Creating a volume
-    Starting a volume
-    Adding a brick
-    Removing a brick
-    Tuning volume options
-    Stopping a volume
-    Deleting a volume 
++ Creating a volume
++ Starting a volume
++ Adding a brick
++ Removing a brick
++ Tuning volume options
++ Stopping a volume
++ Deleting a volume
 
 ### Naming Convention
 While creating the file names of your scripts, you must follow the naming convention followed in your underlying file system like XFS.
@@ -27,37 +26,38 @@ While creating the file names of your scripts, you must follow the naming conven
 ### Location of Scripts
 This section provides information on the folders where the scripts must be placed. When you create a trusted storage pool, the following directories are created:
 
-    /var/lib/glusterd/hooks/1/create/
-    /var/lib/glusterd/hooks/1/delete/
-    /var/lib/glusterd/hooks/1/start/
-    /var/lib/glusterd/hooks/1/stop/
-    /var/lib/glusterd/hooks/1/set/
-    /var/lib/glusterd/hooks/1/add-brick/
-    /var/lib/glusterd/hooks/1/remove-brick/ 
++ `/var/lib/glusterd/hooks/1/create/`
++ `/var/lib/glusterd/hooks/1/delete/`
++ `/var/lib/glusterd/hooks/1/start/`
++ `/var/lib/glusterd/hooks/1/stop/`
++ `/var/lib/glusterd/hooks/1/set/`
++ `/var/lib/glusterd/hooks/1/add-brick/`
++ `/var/lib/glusterd/hooks/1/remove-brick/`
 
 After creating a script, you must ensure to save the script in its respective folder on all the nodes of the trusted storage pool. The location of the script dictates whether the script must be executed before or after an event. Scripts are provided with the command line argument `--volname=VOLNAME` to specify the volume. Command-specific additional arguments are provided for the following volume operations:
 
     Start volume
         --first=yes, if the volume is the first to be started
-        --first=no, for otherwise 
+        --first=no, for otherwise
     Stop volume
         --last=yes, if the volume is to be stopped last.
-        --last=no, for otherwise 
+        --last=no, for otherwise
     Set volume
         -o key=value
-        For every key, value is specified in volume set command. 
+        For every key, value is specified in volume set command.
 
 ### Prepackaged Scripts
 Gluster provides scripts to export Samba (SMB) share when you start a volume and to remove the share when you stop the volume. These scripts are available at: `/var/lib/glusterd/hooks/1/start/post` and `/var/lib/glusterd/hooks/1/stop/pre`. By default, the scripts are enabled.
 
 When you start a volume using `gluster volume start VOLNAME`, the S30samba-start.sh script performs the following:
 
-    Adds Samba share configuration details of the volume to the smb.conf file
-    Mounts the volume through FUSE and adds an entry in /etc/fstab for the same.
-    Restarts Samba to run with updated configuration 
++ Adds Samba share configuration details of the volume to the smb.conf file
++ Mounts the volume through FUSE and adds an entry in /etc/fstab for the same.
++ Restarts Samba to run with updated configuration
 
 When you stop the volume using `gluster volume stop VOLNAME`, the S30samba-stop.sh script performs the following:
 
-    Removes the Samba share details of the volume from the smb.conf file
-    Unmounts the FUSE mount point and removes the corresponding entry in /etc/fstab
-    Restarts Samba to run with updated configuration 
++ Removes the Samba share details of the volume from the smb.conf file
++ Unmounts the FUSE mount point and removes the corresponding entry in
+  /etc/fstab
++ Restarts Samba to run with updated configuration
diff --git a/...dministrator Guide/Linux Kernel Tuning.md → ...dministrator-Guide/Linux-Kernel-Tuning.md b/...dministrator Guide/Linux Kernel Tuning.md → ...dministrator-Guide/Linux-Kernel-Tuning.md
diff --git a/docs/Administrator Guide/Logging.md → docs/Administrator-Guide/Logging.md b/docs/Administrator Guide/Logging.md → docs/Administrator-Guide/Logging.md
diff --git a/...Administrator Guide/Managing Snapshots.md → ...Administrator-Guide/Managing-Snapshots.md b/...Administrator Guide/Managing Snapshots.md → ...Administrator-Guide/Managing-Snapshots.md
diff --git a/docs/Administrator Guide/Managing Volumes.md → docs/Administrator-Guide/Managing-Volumes.md b/docs/Administrator Guide/Managing Volumes.md → docs/Administrator-Guide/Managing-Volumes.md
diff --git a/docs/Administrator Guide/Mandatory Locks.md → docs/Administrator-Guide/Mandatory-Locks.md b/docs/Administrator Guide/Mandatory Locks.md → docs/Administrator-Guide/Mandatory-Locks.md
diff --git a/...dministrator Guide/Monitoring Workload.md → ...dministrator-Guide/Monitoring-Workload.md b/...dministrator Guide/Monitoring Workload.md → ...dministrator-Guide/Monitoring-Workload.md
diff --git a/...uide/NFS-Ganesha GlusterFS Integration.md → ...uide/NFS-Ganesha-GlusterFS-Integration.md b/...uide/NFS-Ganesha GlusterFS Integration.md → ...uide/NFS-Ganesha-GlusterFS-Integration.md
diff --git a/...uide/Network Configurations Techniques.md → ...uide/Network-Configurations-Techniques.md b/...uide/Network Configurations Techniques.md → ...uide/Network-Configurations-Techniques.md
diff --git a/docs/Administrator Guide/Object Storage.md → docs/Administrator-Guide/Object-Storage.md b/docs/Administrator Guide/Object Storage.md → docs/Administrator-Guide/Object-Storage.md
diff --git a/...dministrator Guide/Performance Testing.md → ...dministrator-Guide/Performance-Testing.md b/...dministrator Guide/Performance Testing.md → ...dministrator-Guide/Performance-Testing.md
@@ -64,14 +64,14 @@ capabilities of a distributed filesystem.
 -   [iozone](http://www.iozone.org) - for pure-workload large-file tests
 -   [parallel-libgfapi](https://github.com/bengland2/parallel-libgfapi) - for pure-workload libgfapi tests
 
-The "netmist" mixed-workload generator of SPECsfs2014 may be suitable in some cases, but is not technically an open-source tool. This tool was written by Don Capps, who was an author of iozone. 
+The "netmist" mixed-workload generator of SPECsfs2014 may be suitable in some cases, but is not technically an open-source tool. This tool was written by Don Capps, who was an author of iozone.
 
 ### fio
 
-fio is extremely powerful and is easily installed from traditional distros, unlike iozone, and has increasingly powerful distributed test capabilities described in its --client parameter upstream as of May 2015. To use this mode, start by launching an fio "server" instance on each workload generator host using: 
+fio is extremely powerful and is easily installed from traditional distros, unlike iozone, and has increasingly powerful distributed test capabilities described in its --client parameter upstream as of May 2015. To use this mode, start by launching an fio "server" instance on each workload generator host using:
 
         fio --server --daemonize=/var/run/fio-svr.pid
-        
+
 And make sure your firewall allows port 8765 through for it. You can now run tests on sets of hosts using syntax like:
 
         fio --client=workload-generator.list --output-format=json my-workload.fiojob
@@ -83,14 +83,14 @@ fio also has different I/O engines, in particular Huamin Chen authored the ***li
 Limitations of fio in distributed mode:
 
 -   stonewalling - fio calculates throughput based on when the last thread finishes a test run. In contrast, iozone calculates throughput by default based on when the FIRST thread finishes the workload. This can lead to (deceptively?) higher throughput results for iozone, since there are inevitably some "straggler" threads limping to the finish line later than others. It is possible in some cases to overcome this limitation by specifying a time limit for the test. This works well for random I/O tests, where typically you do not want to read/write the entire file/device anyway.
--   inaccuracy when response times > 1 sec - at least in some cases fio has reported excessively high IOPS when fio threads encounter response times much greater than 1 second, this can happen for distributed storage when there is unfairness in the implementation. 
+-   inaccuracy when response times > 1 sec - at least in some cases fio has reported excessively high IOPS when fio threads encounter response times much greater than 1 second, this can happen for distributed storage when there is unfairness in the implementation.
 -   io engines are not integrated.
 
 ### smallfile Distributed I/O Benchmark
 
 [Smallfile](https://github.com/distributed-system-analysis/smallfile) is a python-based small-file distributed POSIX workload generator which can be used to quickly measure performance for a variety of metadata-intensive workloads across an entire cluster. It has no dependencies on any specific filesystem or implementation AFAIK. It runs on Linux, Windows and should work on most Unixes too. It is intended to complement use of iozone benchmark for measuring performance of large-file workloads, and borrows certain concepts from iozone and Ric Wheeler's fs_mark. It was developed by Ben England starting in March 2009, and is now open-source (Apache License v2).
 
-Here is a typical simple sequence of tests where files laid down in an initial create test are then used in subsequent tests. There are many more smallfile operation types than these 5 (see doc), but these are the most commonly used ones. 
+Here is a typical simple sequence of tests where files laid down in an initial create test are then used in subsequent tests. There are many more smallfile operation types than these 5 (see doc), but these are the most commonly used ones.
 
         SMF="./smallfile_cli.py --top /mnt/glusterfs/smf --host-set h1,h2,h3,h4 --threads 8 --file-size 4 --files 10000 --response-times Y "
         $SMF --operation create
@@ -162,7 +162,7 @@ within that host, and iozone-pathname is the full pathname of the iozone
 executable to use on that host. Be sure that every target host can
 resolve the hostname of host where the iozone command was run. All
 target hosts must permit password-less ssh access from the host running
-the command. 
+the command.
 
 For example: (Here, my-ip-address refers to the machine from where the iozone is being run)
 
@@ -309,7 +309,7 @@ running the "gluster volume profile" and "gluster volume top" commands.
 These extremely useful tools will help you understand both the workload
 and the bottlenecks which are limiting performance of that workload.
 
-TBS: links to documentation for these tools and scripts that reduce the data to usable form. 
+TBS: links to documentation for these tools and scripts that reduce the data to usable form.
 
 Configuration
 -------------
@@ -331,7 +331,7 @@ in order of importance:
 Network configuration has a huge impact on performance of distributed storage, but is often not given the
 attention it deserves during the planning and installation phases of the
 cluster lifecycle. Fortunately,
-[network configuration](./Network Configurations Techniques.md)
+[network configuration](./Network-Configurations-Techniques.md)
 can be enhanced significantly, often without additional hardware.
 
 To measure network performance, consider use of a

diff --git a/...Administrator Guide/Performance Tuning.md → ...Administrator-Guide/Performance-Tuning.md b/...Administrator Guide/Performance Tuning.md → ...Administrator-Guide/Performance-Tuning.md
diff --git a/docs/Administrator Guide/Puppet.md → docs/Administrator-Guide/Puppet.md b/docs/Administrator Guide/Puppet.md → docs/Administrator-Guide/Puppet.md
diff --git a/docs/Administrator Guide/RDMA Transport.md → docs/Administrator-Guide/RDMA-Transport.md b/docs/Administrator Guide/RDMA Transport.md → docs/Administrator-Guide/RDMA-Transport.md
diff --git a/docs/Administrator Guide/SSL.md → docs/Administrator-Guide/SSL.md b/docs/Administrator Guide/SSL.md → docs/Administrator-Guide/SSL.md
diff --git a/...Administrator Guide/Setting Up Clients.md → ...Administrator-Guide/Setting-Up-Clients.md b/...Administrator Guide/Setting Up Clients.md → ...Administrator-Guide/Setting-Up-Clients.md
diff --git a/...Administrator Guide/Setting Up Volumes.md → ...Administrator-Guide/Setting-Up-Volumes.md b/...Administrator Guide/Setting Up Volumes.md → ...Administrator-Guide/Setting-Up-Volumes.md
diff --git a/...e/Split brain and ways to deal with it.md → ...e/Split-brain-and-ways-to-deal-with-it.md b/...e/Split brain and ways to deal with it.md → ...e/Split-brain-and-ways-to-deal-with-it.md
diff --git a/.../Administrator Guide/Start Stop Daemon.md → .../Administrator-Guide/Start-Stop-Daemon.md b/.../Administrator Guide/Start Stop Daemon.md → .../Administrator-Guide/Start-Stop-Daemon.md
Original file line number	Diff line number	Diff line change
Expand Up		@@ -16,7 +16,7 @@ Gluster is a scalable, distributed file system that aggregates disk storage reso
		* Open Source


		![640px-glusterfs_architecture](../images/640px-GlusterFS_Architecture.png)
		![640px-glusterfs_architecture](../images/640px-GlusterFS-Architecture.png)



Expand Down