Lab catalog
found 8 of 778 of 77loading…
Loading…
-
Root partition is full A service stopped saving data: the disk is full. Find what took the space and free it without touching the service's data.~15 min not started
-
Find the actual space consumer The file list says a huge image fills the data volume, yet df disagrees. Find out what really occupies the blocks and write a report without deleting anything.~20 min not started
-
/data is empty after a reboot After a reboot the service cannot find its data: /data is empty. Mount the data disk so that it also mounts at boot.~20 min not started
-
Move the data to a new disk The application's data sits in /srv/data on the root partition, and a new empty disk has been attached for it. Prepare the disk and mount it at /srv/data so that it also mounts after a reboot.~25 min not started
-
Grow the data volume There is almost no space left in /data, and the data must not be deleted. Give the volume more room without repartitioning or losing data.~25 min not started
-
Return a volume to a consistent snapshot A training update damaged the data on a volume, and an LVM snapshot was taken just before it. Roll the volume back to the snapshot and put it back in service.~25 min not started
-
Restore an app from a tar archive The app broke after an update. Prepare a restored copy from the archive next to the working one, complete and with the archived modes.~20 min not started
-
Bring a directory mirror up to date (rsync) A directory mirror has fallen behind its source. Make it an exact copy and leave both the source and the neighbouring data intact.~25 min not started
No lab on the topic you need? Suggest a lab