diff options
| author | hotio <hotio@users.noreply.github.com> | 2018-11-12 16:28:34 +0100 |
|---|---|---|
| committer | Costa Tsaousis <costa@tsaousis.gr> | 2018-11-12 17:28:34 +0200 |
| commit | c3d24687026f5dbc795c3dfc7ebeddcb9664f503 (patch) | |
| tree | a3d46a468d46be66b7a83df392fe8b641a7ab13c /web | |
| parent | 7d617b0f2137bc2e8ab38f17723de4fb6c3c576b (diff) | |
Fix spelling mistake in dashboard_info.js (#4601)
Diffstat (limited to 'web')
| -rw-r--r-- | web/gui/dashboard_info.js | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/web/gui/dashboard_info.js b/web/gui/dashboard_info.js index a873453e5f..0ef39b0992 100644 --- a/web/gui/dashboard_info.js +++ b/web/gui/dashboard_info.js @@ -2021,7 +2021,7 @@ netdataDashboard.context = { }, 'btrfs.disk': { - 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 <code>unallocated</code> may not actually be usable if the volume uses devices of different sizes.', + 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 space listed as <code>unallocated</code> may not actually be usable if the volume uses devices of different sizes.', colors: [NETDATA.colors[12]] }, |