@cryptotaxi247 / netdata-1 / commits / 14243a5dc

Minor updates to the BTRFS chart help text.

* Corrected a typo in the `btrfs.system` chart description. * Added a some info to the `btrfs.disk` chart description to explain that not all the space listed as `unallocated` may be usable. The exact reason for this is somewhat long to explain (in short, it's possible to get a combination of device sizes and chunk profiles that make it impossible to use 100% of the space on all the devices in all cases. For example, a 3-device setup using the `raid1` profile will usually not be able to use 100% of the space on all the devices unless the devices are sized correctly (two devices have to be the same size and the third has to be equal to twice their size minus the size of the system chunk) _and_ added to the volume in a specific order (you have to start with the two smaller ones to force the system chunk to be on them and then add the larger one).

Austin S. Hemmelgarn committed Mar 28, 2018 at 08:13 UTC 14243a5dcd351da6a6be9a8bf59e684412a131f5

1 file changed +2 -2

web/dashboard_info.js

+2 -2

@@ -1905,7 +1905,7 @@ netdataDashboard.context = {

1905 },

1906

1907 'btrfs.disk': {

1908 - info: 'Physical disk usage of BTRFS. The disk space reported here is the raw physical disk space assigned to the BTRFS volume (i.e. <b>before any RAID levels</b>). BTRFS uses a two-stage allocator, first allocating large regions of disk space for one type of block (data, metadata, or system), and then using a regular block allocator inside those regions. <code>unallocated</code> is the physical disk space that is not allocated yet and is available to become data, metdata or system on demand. When <code>unallocated</code> is zero, all available disk space has been allocated to a specific function. Healthy volumes should ideally have at least five percent of their total space <code>unallocated</code>. You can keep your volume healthy by running the <code>btrfs balance</code> command on it regularly (check <code>man btrfs-balance</code> for more info).'

1908 + info: 'Physical disk usage of BTRFS. The disk space reported here is the raw physical disk space assigned to the BTRFS volume (i.e. <b>before any RAID levels</b>). BTRFS uses a two-stage allocator, first allocating large regions of disk space for one type of block (data, metadata, or system), and then using a regular block allocator inside those regions. <code>unallocated</code> is the physical disk space that is not allocated yet and is available to become data, metdata or system on demand. When <code>unallocated</code> is zero, all available disk space has been allocated to a specific function. Healthy volumes should ideally have at least five percent of their total space <code>unallocated</code>. You can keep your volume healthy by running the <code>btrfs balance</code> command on it regularly (check <code>man btrfs-balance</code> for more info). Note that some of the spac elisted as `unallocated` may not actually be usable if the volume uses devices of different sizes.'

1909 },

1910

1911 'btrfs.data': {

@@ -1917,7 +1917,7 @@ netdataDashboard.context = {

1917 },

1918

1919 'btrfs.system': {

1920 - info: 'Logical disk usage for BTRFS system. System chunks store information aobut the allocation of other chunks. The disk space reported here is the usable allocation (i.e. after any striping or replication). The values reported here should be relatively small compared to Data and Metadata, and will scale with the volume size and overall space usage.'

1920 + info: 'Logical disk usage for BTRFS system. System chunks store information about the allocation of other chunks. The disk space reported here is the usable allocation (i.e. after any striping or replication). The values reported here should be relatively small compared to Data and Metadata, and will scale with the volume size and overall space usage.'

1921 },

1922

1923 // ------------------------------------------------------------------------