ceph: troubleshooting: followup reword and small expansion

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2019-04-04 07:48:28 +02:00
parent 6ff32926fc
commit 10df14fb23

View File

@ -537,18 +537,22 @@ pveceph pool destroy NAME
---- ----
Ceph monitoring & troubleshooting Ceph monitoring and troubleshooting
--------------------------------- -----------------------------------
A good start is to monitor the ceph health to begin with. Either through the A good start is to continuosly monitor the ceph health from the start of
ceph tools itself or also by accessing the status through the {pve} initial deployment. Either through the ceph tools itself, but also by accessing
link:api-viewer/index.html[API]. the status through the {pve} link:api-viewer/index.html[API].
If the cluster is in an unhealthy state the commands below will give an The following ceph commands below can be used to see if the cluster is healthy
overview on the current events. ('HEALTH_OK'), if there are warnings ('HEALTH_WARN'), or even errors
('HEALTH_ERR'). If the cluster is in an unhealthy state the status commands
below will also give you an overview on the current events and actions take.
---- ----
ceph -s # single time output
ceph -w pve# ceph -s
# continuously output status changes (press CTRL+C to stop)
pve# ceph -w
---- ----
To get a more detailed view, every ceph service has a log file under To get a more detailed view, every ceph service has a log file under