If you’re experiencing issues with your Ceph storage, you can use the Ceph toolbox.
From the Redgate Clone machine, run the following command to download the Ceph toolbox, which allows you to inspect the contents of the Ceph disk:
curl -O https://raw.githubusercontent.com/rook/rook/master/deploy/examples/toolbox.yaml
This will download the file to your current directory. Run ls to confirm that toolbox.yaml is present.
Next, edit the file using a text editor available on your machine, such as vi, vim, or nano.
Update the namespace at the top of the file to redgate-clone-app, then save your changes.

Once the toolbox file is in place, run the following commands from its directory. Use ls in the terminal to confirm the file is present; if it isn't, navigate to the correct location using cd.
kubectl apply -f toolbox.yaml
After this, if you run a:
kubectl get pods -A
You should see a new pod at the bottom, rook-ceph-tools:
![]()
You can then go into it to run the commands to check the health of the Ceph storage with the below:
kubectl -n redgate-clone-app exec -it deploy/rook-ceph-tools -- bash
You will see on the left that it now says bash as we are in the pod:
ceph status
This will give us some general information about the storage used and its health:
ceph df
It should show the storage used and in which pools.
Type exit to return to the shell, then run the following commands to check the system health.
Check the pod health:
kubectl -n redgate-clone-app get cephcluster
You can also run:
kubectl -n redgate-clone-app get pods kubectl -n redgate-clone-app logs <pod>
This provides health status, capacity, OSD state and error logs. Run the first command to show the pods then copy and paste the name after "logs".
Was this article helpful?
Articles in this section
- Using the CEPH Toolbox
- Changes to SQL Clone In-Product Updates and Notifications
- Failed to clean up temporary user/login. The database principal owns a database role and cannot be dropped
- What resources are required for involved machines using SQL Clone
- Where is the log out button in SQL Clone?
- Only one Rule Controller can be present if the SIMPLELOGINSUB is used
- SQL Clone Download URLs
- SQL Clone performance experiences delays while running simple queries
- Changing the default location of SQL Clone files
- SQL Clone throws "Could not get list of clones" error due to Newtonsoft.Json.JsonSerializationException